[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [wtp-dev] A question about ear->module dependency creation and componentimpl ext.p
- From: Rob Stryker <rob.stryker@xxxxxxxxxx>
- Date: Mon, 23 Feb 2009 13:41:06 +0800
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 126.96.36.199 (X11/20080501)
Dimo: This sounds like the bug over here:
I'd suggest commenting on that bug.
- Rob Stryker
Stoilov, Dimo wrote:
Our project names are different from the Java EE module URIs, and thus
the WTP operation that creates EAR to module dependency generates wrong
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 virtual
component implementation. However it seems only one client can extend
this ext.p. (no priority option defined) and it is already extended by
Any ideas appreciated.
wtp-dev mailing list