Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] A question about ear->module dependency creation and componentimpl ext.p

Actually it's not the same issue. 
Our problem is that the project names are used for reference archive
names during EAR to module reference creation. We don't want this
because our project names are different from the corresponding module


-----Original Message-----
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Rob Stryker
Sent: Monday, February 23, 2009 7:41 AM
To: General discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] A question about ear->module dependency creation
andcomponentimpl ext.p

Dimo:  This sounds like the bug over here:

I'd suggest commenting on that bug.

- Rob Stryker

Stoilov, Dimo wrote:
> Hello,
> Our project names are different from the Java EE module URIs, and thus
> the WTP operation that creates EAR to module dependency generates
> URI in the application.xml. The same is the case with Web->EJB
> dependencies - wrong classpath entry in the manifest.
> As these operations work with the virtual component name (which by
> default is the project name), a possible solution could be to have
> custom component names. If we go for this, we have to use
> org.eclipse.wst.common.modulecore.componentimpl ext.p to provide
> component implementation. However it seems only one client can extend
> this ext.p. (no priority option defined) and it is already extended by
> org.eclipse.jst.j2ee.
> Any ideas appreciated.
> Regards,
> Dimo
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx

wtp-dev mailing list

Back to the top