Hi, Vince
Did you declare this bogus jar as ejb jar? By either having an entry
in application.xml declaring this jar as ejb jar, or having an
ejb-jar.xml/sun-ejb-jar.xml inside the jar? If you declare such bogus
jar as ejb jar, and it is indeed not an ejb jar, there should be warning
messages printed out. But if you didn't declare this jar as ejb jar, it
will just be considered a library jar. :-)
- Hong
Vince Kraemer wrote:
> I have an ear that has two modules. The first is war file and the
> other is an empty jar file.... that I thought was an ejb jar file.
>
> When I deploy this ear, the deploy is successful and there is no
> warning about the bogus ejb-jar... I remember seeing the command fail
> in the past in this kind of situation. is this new behavior
> intentional or have I just encountered a happy accident?
>
> Happy accident: a change in behavior that was unintentional but not
> negative... (I guess)
>
> Oh... V2 b58g
>
> vbk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>