|Think I found problem in J2EE Module Dependencies [message #169608]
||Thu, 18 May 2006 20:26
Originally posted by: y24jds.yahoo.com|
Can somebody back me up on this? I think I found a problem with the J2EE
Module Dependencies option on a Dynamic Web Project.
If you are not familiar with that concept - IBM's WSAD has had it for
several years now - but it lets you take a regular Java project on your
workspace and at run-time have the contents of that java project treated
as sort of a "virtual Jar" with the code visible to the WAR code at
When using Jboss or even Tomcat (using the option to not run directly from
workspace), if you look at the built war file or exploded directory, you
should see the Java project's name in the WEB-INF/lib location. But it
isn't. It is just in the root level of the WAR. As far as I understand,
classloaders will NOT FIND jars that are not in the WEB-INF/lib. Whatever
is packaging the war up needs to place the J2EE Module Dependencies in the
Has anybody else noticed this? Should this be opened as a bug? I've
never opened an Eclipse bug so I am a little hesitant to do so. I tried
searching for this problem but couldnt find an existing report.
|Re: Think I found problem in J2EE Module Dependencies [message #170138 is a reply to message #170062]
||Thu, 25 May 2006 15:35
| Larry Isaacs
Registered: July 2009
Since you are using 3.2 RC5, that would imply you are using WTP 1.5. |
Plug-ins which haven't had to split their development between 1.0.x and
1.5 have kept their 1.0.x numbering in 1.5. WTP 1.5 will use the same,
or possibly newer version, of the 1.0.x version plug-in. I believe the
features will all be 1.5 versions, however.
I'm not certain my assumptions are correct with respect to what you mean
by "virtual jar". It would appear that a bug like:
might apply to the problem you are seeing with JBoss, but I can't say
for sure. Even though this bug is fixed on 5/8, the changes weren't
released to the build until after RC3. Therefore, this fix is not
present in the RC3 release. It will appear in the next WTP 1.5 release.
For Tomcat, maybe this one applies:
I believe this one is included in RC3. Again, there isn't enough detail
in your description to tell for certain if this bug applies.
Jeff Smith wrote:
> I am using the latest 3.2 RC5 and I'm looking for the version and I see
> things like WTP UI Plug-In 1.0.100.v200605040131
> Several other WTP entries that are at 1.0.0.v200605040115
> Even when I do the export War - it isn't placing the "virtual" jars in
> the WEB-INF/lib location - not sure if I said that in my earlier email.
Powered by FUDForum
. Page generated in 0.02678 seconds