Hong Zhang wrote:
>
>> Thanks Paul for letting us know. It is great to see your app
>> deployed fine !
>>
>> "I had to hunt because the log message do not tell from which jar the
>> manifest came from. ", if you have any
>> good suggestion please help us log an enhancement.
> Yeah, if you still have the log message, please send it. We will see
> if we could improve that message by adding the jar information.
Also, please read this blog entry
http://blogs.sun.com/quinn/entry/why_the_warnings_about_glassfish
and see if it describes your situation. From your description it sounds
like this is a similar issue. Note that parts of that entry refer to v2
behavior. Even so, the underlying cause - in which a manifest refers to
a non-existent JAR - can still occur in v3, depending of course on how
the app is packaged.
In the past I've gone back to this code and it's not a trivial one-line
change to add the referring JAR to the error message (currently the
referenced JAR is the only one displayed). Certainly changing this is
possible, but it's a little bit involved and we just haven't had the
time to get to things of this priority.
Please do open an issue if you feel strongly about this.
- Tim
>
> - Hong
>>
>> Happy FishCATting :-)
>> Judy
>>
>> Paul MERLIN wrote:
>>> Hello Hong,
>>>
>>> I found the issue. acme-web-war-0_9_0-SNAPSHOT_war contains a Java Web Start that accidentaly had an ejb-jar in its
>>> dependencies (!!) so there was a jar file containing a @Stateless class located in the acme-web-war-0_9_0-
>>> SNAPSHOT_war directory. Glassfish v2 just ignored the jar files present at a WAR's root.
>>>
>>> All theses changes forced me to clean our packaging up. It's a good thing.
>>>
>>> So ... youhou! ... I finally deployed our app without errors in gf3 ! \o/
>>>
>>> I noticed some warnings in logs, complaining about jar files not found. After a little hunt I found that one of our
>>> dependencies have a manifest with a Class-Path entry. This is a "lib jar" so we never noticed that.
>>> I had to hunt because the log message do not tell from which jar the manifest came from.
>>>
>>> /Paul
>>>
>>>
>>> Le mercredi 14 octobre 2009 15:56:39, Hong Zhang a écrit :
>>>
>>>> Hi, Paul
>>>> Somehow it thinks acme-web-war-0_9_0-SNAPSHOT_war is a ejb jar also,
>>>> what's the contents of this war?
>>>>
>>>> - Hong
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>
>>>
>