This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 304813 - J2ee 1.4 - problem with ejb client project content
Summary: J2ee 1.4 - problem with ejb client project content
Status: RESOLVED FIXED
Alias: None
Product: WTP EJB Tools
Classification: WebTools
Component: jst.ejb (show other bugs)
Version: 3.2   Edit
Hardware: All Windows Vista
: P3 major (vote)
Target Milestone: 3.2 M6   Edit
Assignee: jst.ejb CLA
QA Contact: Kaloyan Raev CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-05 09:07 EST by Krasimir Topchiyski CLA
Modified: 2010-03-08 14:29 EST (History)
4 users (show)

See Also:

Attachments
patch (4.96 KB, patch)
2010-03-05 16:46 EST, Chuck Bridgham CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Krasimir Topchiyski CLA 2010-03-05 09:07:35 EST 
Build Identifier: I20100302-0800

I have executed the WTP smoke tests ( http://wiki.eclipse.org/J2EE_Smoke_Test_%28WTP_3.0%29) and there is a problem:
1.	verify that there is an ejb-client-jar tag in the ejb-jar.xml deployment descriptor -> there is no such tag
2.	EJB interfaces should be in the EJB client project instead in the EJB project -> All classes are in the EJB project, the EJB Client project is empty


Reproducible: Always

Steps to Reproduce:
See here:
http://wiki.eclipse.org/J2EE_Smoke_Test_%28WTP_3.0%29)
Comment 1 Chuck Bridgham CLA 2010-03-05 13:44:27 EST 
Hi - taking a look,

We did make a change late that effected this, rather than reverting, I am confifdent a simple fix can be found quickly - will update asap
Comment 2 Chuck Bridgham CLA 2010-03-05 14:17:51 EST 
Both Carl, and myself can't recreate this behavior...

Is it possible you unchecked "add to Ear"?  This will always skip creating the EJB Client project
Comment 3 Chuck Bridgham CLA 2010-03-05 16:42:00 EST 
After investigating... found that this is a problem with ejb xdoclet processing.

This code was affected by changing how the component references are handled for ejbclient.

The underlying code was using internal api, which is unreliable.

changing to ComponentCore api is recommended.

Attaching patch
Comment 4 Chuck Bridgham CLA 2010-03-05 16:42:41 EST 
After investigating... found that this is a problem with ejb xdoclet processing.

This code was affected by changing how the component references are handled for ejbclient.

The underlying code was using internal api, which is unreliable.

changing to ComponentCore api is recommended.

Attaching patch
Comment 5 Chuck Bridgham CLA 2010-03-05 16:46:45 EST 
Created attachment 161198 [details]
patch
Comment 6 Chuck Bridgham CLA 2010-03-08 14:29:31 EST 
Dropped to HEAD