I forgot to post the detailed error message:
INFO - java.lang.reflect.UndeclaredThrowableException
INFO - $Proxy1.getValueList(Unknown Source)
INFO - cars.aas.fw.client.TestFrame.getStrToBeDisplayed(TestFrame.java:91)
INFO - cars.aas.fw.client.TestFrame.(TestFrame.java:42)
INFO - cars.aas.fw.client.TestFrame.main(TestFrame.java:140)
INFO - sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO - sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
INFO - sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
INFO - java.lang.reflect.Method.invoke(Unknown Source)
INFO - com.sun.javaws.Launcher.executeApplication(Unknown Source)
INFO - com.sun.javaws.Launcher.executeMainClass(Unknown Source)
INFO - com.sun.javaws.Launcher.continueLaunch(Unknown Source)
INFO - com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
INFO - com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
INFO - com.sun.javaws.Launcher.run(Unknown Source)
INFO - java.lang.Thread.run(Unknown Source)
Do you get warnings from the verifier when you deploy your bean?
I dont know if this helps, but i got the same exception when i was migrating from 3.0.4 to 3.2.1. In my case, the error was because i was using a Stateless Session Bean configuration whose "invoker-proxy-binding-name" element was no longer valid in 3.2.1.
when i checked the configurations my error was resolved
No, I don't get any warings or errors for this when I deploy the bean. It is a runtime exception.
I believe the invoker-proxy-binding-name you mentioned is specified in standardjboss.xml in server/conf and I use the default setting. Could you tell me how you change it? I use the version 3.2.1, too.
if you are using the default configurations then you should not have any problems.
in my case i was using the jboss.xml file that i had created for 3.0.4 and when i deployed on 3.2.1 those settings for container configuration were not valid.
are you by any chance trying to migrate to 3.2.1 from an earlier version ?