Bug 877055 - Seam 2.3 seam-gen generated project in JBDS has error in ActionTest, no return statement in createDeployment
Summary: Seam 2.3 seam-gen generated project in JBDS has error in ActionTest, no retur...
Keywords:
Status: CLOSED DUPLICATE of bug 877063
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Seam
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 2.2.0
Assignee: Marek Novotny
QA Contact: Marek Schmidt
URL:
Whiteboard: Seam 2.3 seam-gen
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-15 15:42 UTC by Ron Šmeral
Modified: 2016-11-01 01:36 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-20 15:44:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 877063 0 unspecified CLOSED Seam 2.3 seam-gen generated project is not testable 2021-02-22 00:41:40 UTC

Internal Links: 877063

Description Ron Šmeral 2012-11-15 15:42:48 UTC
Description of problem:
If a seam-gen generated project with a seam-gen generated action is imported into JBDS, it reports a problem in the test for the action, because the createDeployment method has the return statement commented out.

Version-Release number of selected component (if applicable):
WFK 2.1.0.CR2 jboss-seam-2.3.0.Final-redhat-1, JBDS 5.0.1.GA

How reproducible:
Import a seam-gen generated project into JBDS.

Steps to Reproduce:
1. seam create-project new-action 
2. Import into JBDS.
  
Actual results:
JBDS problem (error):
  This method must return a result of type WebArchive	CompTest.java	/testprojectEAR/src/test/com/mydomain/testprojectEAR/test	line 19	Java Problem

Expected results:
No errors.

Comment 4 mark yarborough 2012-11-19 14:47:13 UTC
Move to WFK 2.2 and release note for WFK 2.1 per 19-Nov triage call.

Comment 5 Marek Schmidt 2012-11-20 15:44:57 UTC

*** This bug has been marked as a duplicate of bug 877063 ***

Comment 6 Marek Schmidt 2012-11-21 16:21:11 UTC
This duplicate issue should not contain release notes. The current text is wrong anyway, more accurate description is in the BZ#877063 (of which this issue is a duplicate)


Note You need to log in before you can comment on or make changes to this bug.