[JBossWS] - JBossWS 1.2.1 issues
by tzhou
I've been using JBossWS 1.2.1 along with Sun's Wiseman API for WS-Management development. Let's say it's an eye-opening experience. After days of hard debugging, here are some of the issues (or non-issues) I found. Either case, I hope my time spent can be of some value.
1. WRONG_DOCUMENT_ERR when marshaling a SOAP document complaining that caller tries to append a node to another node that belongs to a different owner document
Turns out the problem was caused by DOMUtils, which uses ThreadLocal to keep track of owner document. This would work fine if everything is in the same thread. But in my case, Wiseman code constructs a response message, and then pass that response object to a separate handler thread for further processing. And that becomes a _problem_. I'm not sure about the rationale behind the threadlocal mechanism, but to me assuming all DOM processing is in one thread is simply dangerous. Thoughts?
2. JAXB and JBossWS compatibility issue
The upper-level code (Wiseman) constructs a SOAP message, and uses JAXB to marshal content to the body, something like "marshaller.marshal(contentObj, getBody())". The result: only the top-level node gets added to the body, but not its decedents. After some digging, I found the problem was caused by SOAPBodyImpl.appendChild(), which constructs a new child from the existing child node. This apparently is a problem for JAXB, since the subsequent tree construction is all based on the original child node.
FYI, I'm using JBossWS 1.2.1GA.
-Ting
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043805#4043805
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043805
18 years, 4 months
How to change the context of the wsdl url?
by Rick Reumann
I would have thought there would be an annotation on the WebService
annotation to do this, but I can't seem to find one...
What I need is a way to change the context of the generated wsdl url.
I would think this question would come up quite frequently since often
times the server you deploy to might have a different context then
what users might use to access the application. Maybe I'm just
googling poorly, but any help would be appreciated.
--
Rick
18 years, 4 months
[JBossWS] - Generate JBossWS Artifacts: Error occurs
by MichelRobert
Hello,
When I attempt to generate JBossWS Artifacts, a NullPointerException
occurs upon a call to handleWSDLToJavaGeneration(...).
I've looked on line for clues to this behavior, and found several references to this problem. The only 'suggested fix' is to make sure that wstools-config.xml is in the path.
Although it does look like the problem is a "file not found" type-of-error, I do not understand why JBossWS would have any trouble finding a temporary file it created (wstools-config49256.xml). So perhaps the problem is elsewhere?
Any ideas? It looks like this problem has been encountered before, and the solution is probably something really simple!
Below is the log that is displayed in the console window:
Running JBossWS wstools for [HelloWorld]
directory: E:\java\jboss-4.0.5.GA\bin
command: cmd.exe /C wstools.bat -config C:\DOCUME~1\MRS\LOCALS~1\Temp\wstools-config49256.xml -dest E:\java\Eclipse4Jbossws\workspace\mm3\src
=============================================="
.
WSTools Environment
.
JBOSS_HOME: E:\java\jboss-4.0.5.GA\bin\\..
.
JAVA: E:\java\jdk6\bin\java
.
JAVA_OPTS:
.
==============================================="
.
Exception in thread "main" java.lang.NullPointerException
at java.io.File.(File.java:222)
at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:282)
at org.jboss.ws.tools.WSTools.process(WSTools.java:137)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:69)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
This is wstools-config49256.xml (formatted for legibility):
===============================================
<?xml version="1.0" encoding="UTF-8"?>
<jbos:configuration xmlns:jbos="http://www.jboss.org/jbossws-tools">
<jbos:wsdl-java file="C:\DOCUME~1\MRS\LOCALS~1\Temp\tempdir49257.tmp\HelloWorld.wsdl" unwrap="true">
<jbos:mapping file="jaxrpc-mapping.xml"/>
</jbos:wsdl-java>
</jbos:configuration>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043697#4043697
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043697
18 years, 4 months
Patching 4.0.5 with EJB 3.0 RC6 - PFD, then install JBossWS - question
by Rick Reumann
Currently we are patching JBoss 4.0.5 with the EJB 3.0 RC6 PFD patch found here:
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=13...
I would then like to make sure we can leverage JAX-WS, so I'm
following the install guide of jbossWS at
http://jbws.dyndns.org/mediawiki/index.php/Install_JBossWS
One of things I noticed is that the first patch removes the
jbossws14.sar and adds a file (not a dir) of "jbossws.sar." Then the
jbossws ant install for jboss4.0 tries to remove either of the dirs
"jbossws.sar" or "jbossws14.sar" and replace it with it's version of
the jbossws.sar. The install fails here since the first patch added a
file not a dir - an easy fix to the install.xml of the jbossws with
the added line fixes this..
<delete file="${jboss40.home}/server/${jboss.server.instance}/deploy/jbossws.sar"
/>
I'm wondering is there are any other issues to be aware of following
this procedure of patching 4.0.5 with the EJB3.0 patch and then
installing jbossws?
I guess we could just be safer and use the jems installation of 4.0.5
and then install jbossws. (I just know we had things working pretty
well with the patched version, so I'm not wanting to change too much
at once.)
18 years, 4 months
[JBossWS] - After Adding WSDL to JBossWS, the
by MichelRobert
Hello,
I seem to have some sort of configuration problem. When I "Add a WSDL" to my project using JBossWS, the IDE reads in the wsdl, but does not actually populate the "JBossWS Web Services" entry in package Explorer. After lots of tests, I finally manged to get an error message:
"Error importing wsdl: org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA"
Note the wsdl does not contains any CDATA. In fact, this is the wsdl that is generated by JBossIDE from the basic HelloWorld example. So you would think it would not object to anything in it!
I should also mention that it is my understanding that when the JbossIDE generates the wsdl, that a wsdl entry should appear under "JBossWS Web Services". This does not happen in my IDE (which is the "JBoss Bundle" that includes Eclipse). The wsdl is actualy created though.
Any help anyone might offer to help resolve this problem would be greatly appreciated.
MR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043475#4043475
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043475
18 years, 5 months