Hi, Wouter
I think you hit this packaging issue in NetBeans:
http://www.netbeans.org/issues/show_bug.cgi?id=173195
While the more portable approach is to package ejb interface in the
war (or in the ear lib), removing the manifest entry from war would work
with glassfish (as in glassfish impl, the classloader loading ejbs is
the parent classloader of the war, so war classes can see ejb classes
automatically if they are packaged inside the same ear).
- Hong
Wouter van Reeven wrote:
>Hi once more,
>
>
>And it also works on build 68. Also from NetBeans now I resolved my
>packaging issues. I will close the issue I reported.
>
>
>Thanks, Wouter
>
>On Wed, Oct 21, 2009 at 02:43:32PM +0200, To quality wrote:
>
>
>>Hi again,
>>
>>
>>Hmm this is really weird. I unchecked the option to package the EJB jar
>>file in the WAR and now deployment using asadmin works fine. However,
>>when I inspected the WAR there was no EJB jar in it! Really strange...
>>Anyway, it seems to work now on b66.
>>
>>
>>Thanks, Wouter
>>
>>On Wed, Oct 21, 2009 at 02:40:26PM +0200, To quality wrote:
>>
>>
>>>Hi all,
>>>
>>>
>>>Today I am working on my presentation for the JFall conference in the
>>>Netherlands in November again. Unfortunately, when I try to deploy my
>>>EAR from NetBeans to build 68 an exception occurs for which I have filed
>>>an issue last week.
>>>
>>>So I tried to deploy to GlassFish using asadmin and that fails as well.
>>>I then tried to deploy to build 66 using asadmin as well, and that fails
>>>too. But deploying to build 66 using NetBeans works just fine!
>>>
>>>The error I get when deploying using asadmin is
>>>
>>>com.sun.enterprise.admin.cli.CommandException: remote failure: Exception
>>>while deploying the app : java.lang.RuntimeException: Cannot resolve
>>>reference Local ejb-ref name=jf2009Session,Local 3.x interface
>>>=nl.amis.jfall2009.ejb.session.JFall2009SessionLocal,ejb-link=null,lookup=null,mappedName=,jndi-name=,refType=Session
>>>because there are 2 ejbs in the application with interface
>>>nl.amis.jfall2009.ejb.session.JFall2009SessionLocal
>>>
>>>Since this is a JEE5 application, I have both an interface named
>>>JFall2009SessionLocal annotated with the @Local annotation and a class
>>>named JFall2009SessionBean annotated with @Stateless implementing the
>>>interface.
>>>
>>>In EJB 3.1 the interface is not needed anymore. However, when I remove
>>>the interface and make sure my other classes use the Bean class instead
>>>of the Local interface, deployment with asadmin still gives the same
>>>error and deploying from NetBeans goes ok.
>>>
>>>Would anyone know what's going on?
>>>
>>>
>>>Thanks, Wouter
>>>
>>>--
>>>Lime and limpid green a second scene,
>>>A fight between the blue you once knew.
>>>Floating down the sound resounds
>>>Around the icy waters underground
>>>[Pink Floyd - Astronomy Domine]
>>>
>>>Skype: wvreeven
>>>Facebook: wvreeven
>>>Twitter: wvreeven
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>>For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>
>>>
>>--
>>Lime and limpid green a second scene,
>>A fight between the blue you once knew.
>>Floating down the sound resounds
>>Around the icy waters underground
>>[Pink Floyd - Astronomy Domine]
>>
>>Skype: wvreeven
>>Facebook: wvreeven
>>Twitter: wvreeven
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>
>>
>
>
>