[JBoss AOP] - anyway to do loadtime aop without javaagent?
by null null
null null [http://community.jboss.org/people/deanhiller] created the discussion
"anyway to do loadtime aop without javaagent?"
To view the discussion, visit: http://community.jboss.org/message/605525#605525
--------------------------------------------------------------
We are using annovention to scan for annotations which means our Class is not loaded since it just reads the bytecode. I then have a list of all the classes I want to insert two methods into(readObject/writeObject) and add the Serializable interface too(very special platform targeted at specific problem).
Soooo, now that I have the classname and it is NOT in the classloader, I would really like to load the class now without any tweaks to the command line so all the unit tests keep working without developers having to change their config for every test case. Ideally, we don't want compile time weaving since developers run the unit tests from eclipse as well.
I am assuming, I could setup a classloader and that hopefully jbossAOP already has a classloader I can just wire in and maybe feed this special list of classes into that classloader as I discover them???
thanks for any help/pointers to more docs on this.
Dean
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605525#605525]
Start a new discussion in JBoss AOP at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
[JBoss Web Services] - JAX-WS in JBoss AS 6
by Jarod Rose
Jarod Rose [http://community.jboss.org/people/grodd] created the discussion
"JAX-WS in JBoss AS 6"
To view the discussion, visit: http://community.jboss.org/message/605703#605703
--------------------------------------------------------------
Hello,
I'm currently working on getting a service that is implemented using jax-ws 2.2.3 and Spring migrated from JBoss 4 to JBoss 6 and I'm having issues with the service conflicting with the JBoss CXF deployer that comes with JBoss 6. Currently when my application tries to instantiate the service I get the following exception.
java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider org.jboss.wsf.stack.cxf.client.ProviderImpl could not be instantiated: java.lang.ClassCastException
at java.util.ServiceLoader.fail(ServiceLoader.java:207)
at java.util.ServiceLoader.access$100(ServiceLoader.java:164)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:353)
at java.util.ServiceLoader$1.next(ServiceLoader.java:421)
at javax.xml.ws.spi.Provider.getProviderUsingServiceLoader(Provider.java:180)
at javax.xml.ws.spi.Provider.provider(Provider.java:140)
at javax.xml.ws.Service.<init>(Service.java:92)
at com.micros_retail.xcenter.serenade.CWMessageInService.<init>(CWMessageInService.java:42)
at com.micros_retail.xcenter.serenade.SerenadeEndpoint.callSerenade(SerenadeEndpoint.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.integration.util.DefaultMethodInvoker.invokeMethod(DefaultMethodInvoker.java:97)
at org.springframework.integration.handler.MessageMappingMethodInvoker.doInvokeMethod(MessageMappingMethodInvoker.java:135)
at org.springframework.integration.handler.MessageMappingMethodInvoker.invokeMethod(MessageMappingMethodInvoker.java:107)
... 54 more
Caused by: java.lang.ClassCastException
at java.lang.Class.cast(Class.java:2990)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:345)
... 67 more
I tried override which provider to use by specifying it in META-INF/services/javax.xml.ws.spi.Provider but that didn't do any good. I'm still new to CXF and JAX-WS so any help/info would be appreciated.
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605703#605703]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
[JBoss Messaging] - JMS client unable to receive messages from server
by Vijay Ivaturi
Vijay Ivaturi [http://community.jboss.org/people/vkivaturi] created the discussion
"JMS client unable to receive messages from server"
To view the discussion, visit: http://community.jboss.org/message/605652#605652
--------------------------------------------------------------
Hi,
I'm using JBoss 5.1.0.GA. There are 2 instances. One instance has ESB and some web services running. ESB has JMS listeners configured and triggers the web services. This setup works when I use a standalone Java JMS client to send request message and receive the reponse from reply queue.
Now, I moved the same standalone client code to a web application, again running on a different JBoss 5.1.0 GA instance. The message is sent successfully from client application. On server side, ESB picks it up, calls the web service and sends the reply JMS message back.
But the client application is not able to process the reply message. Immediately after "TextMessage message = (TextMessage) receiver.receive()", following exception is thrown:
16:15:56,125 ERROR [ServerInvoker] Error executing server oneway invocation request: InvocationRequest[16a6469, CALLBACK, InternalInvocation[1e63688]] org.jboss.remoting.callback.HandleCallbackException: Unknow callback type: InvocationRequest[10af156, ClientDelivery[JBossMessage[21391428092411916]:PERSISTENT]] at org.jboss.jms.client.remoting.CallbackManager.handleCallback(CallbackManager.java:125) at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1628) at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:863) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:878) at org.jboss.remoting.ServerInvoker$1.run(ServerInvoker.java:2026) at org.jboss.jms.server.remoting.DirectThreadPool.run(DirectThreadPool.java:63) at org.jboss.remoting.ServerInvoker.handleOnewayInvocation(ServerInvoker.java:2037) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:861) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
I read in this forum that such issue happens when different versions of JBoss are used; but I have both the client and server applications on 5.1.0.GA.
Please let me know if there are any potential classpath or version issues I should look out for.
Thanks
Vijay
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605652#605652]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month