[JBoss Web Services] - Bizarre Serialization Problem
by spyhunter99
spyhunter99 [https://community.jboss.org/people/spyhunter99] created the discussion
"Bizarre Serialization Problem"
To view the discussion, visit: https://community.jboss.org/message/728819#728819
--------------------------------------------------------------
I'm looking at WS-Discovery, which is a UDP SOAP over multicast based protocol that is similar to UDDI, except way similier and it's adhoc. In the Java world, there's only one implementation that I've found which is here http://code.google.com/p/java-ws-discovery/ http://code.google.com/p/java-ws-discovery/.
I can get the samples to run correctly in outside of the Jboss world and it works as advertised. Basically, there is a service that listens for "Probe" messages on UDP and replies to the requestor based on the search criteria. Cool.
The problem I ran into boils down to a serialization issue. Escentially, when I run outside of Jboss, it's using the standard default JDK soap libraries, aka Sun's JAXB serializers, message factories and marshallers. In Jboss, it's actually creating JbossWS classes which fill these roles. For everything I've done up until now, this have been just fine with this arrangement. Enter WS-Discovery (at least this guys implementation).
First, some implementation details that are worth mentioning and are important to understanding the problem. It's not SOAP over HTTP, it's over UDP which means this guys library serializes the message, then writes it to transport. In order to facilitate this, the author created a custom class which has functions such as getSOAPmessage and getSOAPbody etc with a toString function that serializes the message. The problem is related to how the message is structured and as you can imagine, using the JDK's classes it correctly serializes but with the JbossWS classes it does not. Specifically, the part with the search results is null under JbossWS.
It appears that the actually loading of the JAXB specific stuff happens with this line, which unfortunately doesn't leave me with any flexiblity as far as forcing it to the JDK's vs JbossWS.
MessageFactory factory = MessageFactory.newInstance(soapProtocol);
At the point of serialization, the SOAP message itself is
com.sun.xml.internal.messaging.saaj.soap.ver1_2.Message1_2Impl
org.jboss.ws.core.soap.SOAPMessageImpl
Long story short, there is a way to force the class loading from a specific instance to use Sun's JDK? Or perhaps would it be better if I found either an alternative implementation or write my own.
Esscentially what I would like to do is to write a JAX-WS handler which does a web service callout using WS-Discovery to find the correct url, thus eliminating the need for configuration files. It obviously would need to work in a variety of soap stacks, more than just JbossWS and Sun's default implementation.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/728819#728819]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years
Re: [jboss-user] [JBoss Tools] - m2e(clipse)-wtp 0.15.0 : New and Noteworthy
by lostiniceland
lostiniceland [https://community.jboss.org/people/lostiniceland] commented on
"m2e(clipse)-wtp 0.15.0 : New and Noteworthy"
To view all comments on this blog post, visit: https://community.jboss.org/community/tools/blog/2012/02/03/m2eclipse-wtp...
--------------------------------------------------
Thanks for the work on this highly-anticipated-plugin.
I do have a little problem though. I used version 0.14 with an JBoss example on my laptop and there everythin works fine, so I introduced the plugin to my project and I installed 0.15. We are (unfortunately) stuck at JEE 5 and when I import the Maven project, m2e-wtp generates another project which has the name of my <webmodule>EAR. This seems to be a virtual component and I am getting error when trying to look at the Deployment Assemblies in the projects properties
The only difference is the plugin version and the JEE5 < - > JEE6 difference. Both projects have a ear-module but on JEE5 with version 15 I get this additional project instead that the ear-module is configured.
Can someone explain why this might happen?
--------------------------------------------------
14 years
[jBPM] - JBPM Console Server (5.2)/Hibernate/JBoss AS 7.1.1 Error
by Timothy Charman
Timothy Charman [https://community.jboss.org/people/tcharman] created the discussion
"JBPM Console Server (5.2)/Hibernate/JBoss AS 7.1.1 Error"
To view the discussion, visit: https://community.jboss.org/message/728888#728888
--------------------------------------------------------------
Hi
I get this when trying to click on a process in the JBPM console. It is obviously trying to connect to the console server database for the first time, and failing. It has retrieved the process from Guvnor successfully (apparently). Anyone have any ideas? It looks like it might have found Hibernate 4 but is coded against Hibernate 3?
Thanks
Tim
URL: ' http://xxx.xxx.xxx.xxx:8080/gwt-console-server/rs/process/definition/timi... http://xxx.xxx.xxx.xxx:8080/gwt-console-server/rs/process/definition/timi...'
Action: 'org.jboss.bpm.console.client.process.UpdateInstancesAction'
Exception: 'class com.google.gwt.http.client.RequestException'
HTTP 500:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.jboss.resteasy.spi.UnhandledException: java.lang.NoSuchMethodError: org.hibernate.SessionFactory.getCurrentSession()Lorg/hibernate/classic/Session;
org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:340)
org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214)
org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190)
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:540)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
root cause
java.lang.NoSuchMethodError: org.hibernate.SessionFactory.getCurrentSession()Lorg/hibernate/classic/Session;
org.jbpm.process.audit.ProcessInstanceDbLog.findActiveProcessInstances(ProcessInstanceDbLog.java:46)
org.jbpm.integration.console.CommandDelegate.getActiveProcessInstanceLogsByProcessId(CommandDelegate.java:300)
org.jbpm.integration.console.ProcessManagement.getProcessInstances(ProcessManagement.java:66)
org.jboss.bpm.console.server.ProcessMgmtFacade.getInstancesJSON(ProcessMgmtFacade.java:189)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:616)
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:155)
org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
note The full stack trace of the root cause is available in the JBoss Web/7.0.13.Final logs.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/728888#728888]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years