2 Replies Latest reply on Jun 13, 2006 5:02 AM by dreuzel

    putting classes  in  bean requests   not Consistent  !!!!!??

    dreuzel Jun 9, 2006 11:14 AM

      I wrote several working beans (I.m using a local bean, call by reference,...
      sharing the information using EJB 3.0

      and for all those beans i get the same problem


      String xx=bean.routine( Class )

      the class is defined as in the interface of caorse
      otherwize there is a compilation error ....

      as the class is of type String all seems ok
      as the class is of type HashMap<String,class>
      it seems to pass but the class defintion on the other side is corrupted
      as the class is of type Document (dom4J) all seems ok
      as I use one of my classes to be passed as arguments

      an ececution I get Illegal argument

      javax.ejb.EJBException: java.lang.IllegalArgumentException: Wrong target. class com.cyclus.bean.DommerBean for public java.lang.String com.cyclus.bean.DommerBean.DomSession(com.cyclus.Dom.DomInfo)
      at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
      at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
      at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:197)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(Meth16:49 9/06/2006odInvocation.java:101)
      at org.jboss



      Can anyone help me on this ?????
      This seems as if BEANS DO NOT WORK AT ALL

      • 1189 Views
      • Tags:
        • 1. Re: putting classes  in  bean requests   not Consistent  !!!
          bdecoste
          bdecoste Jun 9, 2006 7:11 PM (in response to dreuzel)

          Can you post the bean implemention and interfaces along with the client code?

            • Actions
          • 2. Re: putting classes  in  bean requests   not Consistent  !!!
            dreuzel Jun 13, 2006 5:02 AM (in response to dreuzel)




            setting "UseJBossWebLoader" true in
            Confirms there is definitly a problem.
            Only the problem get Worse

            C:\JBOSS\jboss-4.0.4.GA\server\default\deploy\jbosswebtomcat55.sar\META-INF\jboss-service.xml



            Using Jboss 4.0.4.GA local interfaces
            Does definetly Corrupt the presentation of the ECLIPSE Debugger.
            Even after a complete rebuild locations and traps are placed completly (let's say at random) all references have gone


            I seem to have an additional problem corrupting the result

            I verify the bean interface to be correct as I setup a JNDI Connection
            (on servlet side)

            JNDI beancalss ->>>> Beaner
            beaner =Ctx.lookup(beanName)
            if (beaner instanceof bean)
            else ----> Beaner not derived from overall Bean Class


            Appearently the Jboss-tomcat servlet does not recogise
            beans passed from JNDI ??
            an other classloader problem ???? works perfectly as
            UseJBossWebLoader=false

            still trying to confirm/deney the original

            Summary
            UseJBossWebLoader=false
            ECLIPSE_JBOSS debugging syncronisation OK
            JNDI --> Classes are recognised

            UseJBossWebLoader=true
            ECLIPSE_JBOSS debugging syncronisation FAILS !!!!
            JNDI --> Classes not recognised any more.
            as far as can be seen the problem is NOT SOLVED
            Still class desynchronisation beween Servlet and BEAN !!!!




            Any other suggestions ?



              • Actions