please help arguments of a bean CALL depends on runtime

[dreuzel]

I setup my beans (i assume correctly since it works for a while)
This is getting very urgent and I'm very worried over using beans ever again....

example String xxx=bean.myroutine(String xxxx) ; works OK
example String xxx=bean.myroutine(HashMap<String,String> xxxx) ; works OK
example String xxx=bean.myroutine(Document xxxx) ;(DOM4j works OK


as I use my own classes containing just data
ex: public class yyy
{String abcv;
String xyz;
} (or anything self defined ....)

example String xxx=bean.myroutine((yyy) aas) ;It fails with :

of coarse I'm addapting the call every time .....
i seem to get this with every bean in my system
both client and server have the class defined in the same jar path ...
it realy seems to have to do with

MY Classes versus external classes
Using jboss 4.0.4. GA

javax.ejb.EJBException: java.lang.IllegalArgumentException: Wrong target. class Bean for public java.lang.String com.cyclus.bean.DommerBean.DomSession(com.cyclus.Dom.DomTransport)
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(MethodInvocation.java:101)
at org.jboss.ejb3.service.ServiceContainer.localInvoke(ServiceContainer.java:199)
at org.jboss.ejb3.service.ServiceLocalProxy.invoke(ServiceLocalProxy.java:75)
at $Proxy79.DomSession(Unknown Source)
Wrong target. class bean.DommerBean for public java.lang.String Bean.DomSession(Dom.DomTransport)

[dreuzel]

more information


I see 3 area's of attention

a) the client (works perfect localy)
b) the interface (EJB argument verification)
c) the service (works perfect localy )

S0 some problem occurs in the EJB interface argument verification

the service is never called any way ...


hOW CAN i MANIPULATE THAT ????

[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 ?