[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-28 Thread green_bean_1
So.. I think I have finally narrowed it down with the help of ALR and mopuf. props to you both. it appears that if I annotate the beans with a specific @Stateless.name and use @EJB.beanName things work fine. but, if i let the container use the default name (which I understand to be just the

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-28 Thread green_bean_1
EJB.name does NOT work. it does NOT correctly "inject" the specific implementation.. How would I verify the ENC name for each specific implementation? anonymous wrote : | 2.If two bean are implementing the same interface (strategy which is not desirable) then you shod use the beanName at

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-28 Thread ALRubinger
"green_bean_1" wrote : EJB.name does NOT work. it does NOT correctly "inject" the specific implementation.. How would I verify the ENC name for each specific implementation? You haven't supplied the right ENC name yet, so how can you assert it doesn't work? :P. Get the ENC Name using JNDIView

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-28 Thread mopuf
hi, IMHO here we deal here with two problems (at least), one of my first question is which is your goal ? Here are my answers to your problem : 1.The EJBs does JNDI behind the scene and to solve this you must help him a little - with some configuration files. 2.If two bean are implementing the s

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-28 Thread ALRubinger
So you're still exhibiting unexpected behaviour? Does @EJB.name work as expected (ie resolves properly to the ENC name)? I'd be surprised if it didn't as we're shipping a compliant implementation. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198141

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-28 Thread green_bean_1
ok.. so.. i lied.. the @EJB(mappedName) variation works.. its just the @EJB(name=) variation that doesn't work.. in my ejb-jar.xml file there is an entry for the StatelessLifecycleBean but not for the HelloWorldStatelessBean.. s View the original post : http://www.jboss.com/index.html?module=

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-28 Thread green_bean_1
As for my platform, I am using jboss-5.0.0.GA on OS X 10.5.6 using JDK 1.5.0_16.. In regards to the comments / questions dealing with the mappedName v. name.. the example yields the same results whether I am using mappedName or name. in other words.. @EJB(name="javaEEApplication/HelloWorldSta

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-28 Thread green_bean_1
sorry.. the code should be: @EJB(mappedName="javaEEApplication/HelloWorldStatelessBean/remote-com.di.examples.HelloWorld") HelloWorld helloWorld; @EJB(mappedName="javaEEApplication/StatelessLifecycle/remote-com.di.examples.HelloWorld") HelloWorld lifecycle; @EJB(name="HelloWorldS

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-18 Thread ALRubinger
Judging from those JNDI Names, gotta be at least AS 5 CR2. :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197506#4197506 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197506 _

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-18 Thread jaikiran
In addition to what Andrew said, which version of JBossAS do you use? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197504#4197504 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197504 _

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-18 Thread ALRubinger
"green_bean_1" wrote : So, it seems to me like if two impls share the same interface, JBoss doesn't differentiate them? If you can provide a use case (unit test) exhibiting this, we can open a JIRA for resolution. :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op

[jboss-user] [EJB 3.0] - Re: Possible Bug?

2008-12-18 Thread ALRubinger
@EJB.name is for the JNDI name of the reference within the ENC. Check your JNDI View, looking under the component (your EJB's deployment) namespace for the correct value. If you're like to use the global JNDI name (as you are), use @EJB.mappedName. Or, designate the target EJB by its name: @EJ

[jboss-user] [EJB 3.0] - Re: Possible Bug related top DiscriminatorFormula

2008-09-20 Thread jaikiran
Since this is specific to Hibernate, i think you will have to report this in Hibernate forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177786#4177786 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177786 ___

[jboss-user] [EJB 3.0] - Re: Possible Bug related top DiscriminatorFormula

2008-09-19 Thread ablevine1
Here it is: | DEBUG [SocketServerInvokerThread-172.16.200.111-0][2008-09-18 10:40:50,914][com.squaretrade.category.CategoryManagerSessionImpl] CategoryManagerSessionImpl.java(114): CAUGHT EXCEPTION WHEN LOOKING UP CATEGORY | javax.persistence.PersistenceException: org.hibernate.WrongClassExc

[jboss-user] [EJB 3.0] - Re: Possible Bug related top DiscriminatorFormula

2008-09-18 Thread jaikiran
Please post the entire exception stacktrace. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177559#4177559 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177559 ___ jboss-use

[jboss-user] [EJB 3.0] - Re: Possible bug? EJB3 in a .sar

2007-01-15 Thread adamw
Hello, I forgot to write about the environment :) So, I'm using AS 4.0.5 with ejb3 rc9 patch1. The exception happens when the .ejb3 contains a @Service annotated class. The start() method compeltes successfully, then the exception is thrown and the service is stopped (the stop() method is calle