[JBossWS] - Re: java.lang.UnsupportedOperationException when connecting
by rayymlai
this seems to be a compatibility issue of JBossWS 1.0.x with Java SE 6.0's JAX-WS 2.0. I've siimlar problem.
I had the JSR181EJB3 example from JBossWS 1.0.3/1.0.4 running well on JBoss AS 4.0.4/4.0.5 (after some painful patches). After I upgrade my JDK to 6.0, the same example generates the exception UnsupportedOperationException.
I try to remove the javax.xml.SOAPMessage*.class from the jbossws-client.jar and let the example uses Java SE 6.0's JAX-WS API. but it seems that there are more APIs impacted.
Previous email threads mention JDK 6.0 beta. But the same exception occurs for the GA version of 6.0 as well.
Java SE 6.0 provides amazing JAXWS 2.0 support. You can use its embedded HTTP web server to publish web services. New JAXWS 2.0 APIs are provided. I'd assume the current JBossWS 1.0.4's JAXWS API is not sync up with the latest JAXWS 2.0 yet.
Perhaps JBossWS team can advise the compatibility issue. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993905#3993905
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993905
17 years, 5 months
[JBossWS] - Cound Not obtain the Java Type Mapping-What is wrong where t
by pshankar
I am getting the Java type mapping error even after packaging/placing the mapping class within the WAR/Server
Where exactly should the file go?
The class is built within war and also the descriptor files are there.
org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://DefaultNamespace}ArrayOf_tns2_anyType at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataR
|
My jaxrpc-mapping.xml read below
<?xml version="1.0" encoding="UTF-8"?>
| <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
| http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd"
| version="1.1">
| <package-mapping>
| <package-type></package-type>
| <namespaceURI>http://MySpringService</namespaceURI>
| </package-mapping>
| <service-interface-mapping>
| <service-interface>MySpringService.MySpringServiceService</service-interface>
| <wsdl-service-name xmlns:serviceNS='http://DefaultNamespace'>serviceNS:MySpringServiceService</wsdl-service-name>
| <port-mapping>
| <port-name>MySpringService</port-name>
| <java-port-name>MySpringService</java-port-name>
| </port-mapping>
| </service-interface-mapping>
| <service-endpoint-interface-mapping>
| <service-endpoint-interface>MySpringService.MySpringService</service-endpoint-interface>
| <wsdl-port-type xmlns:portTypeNS='http://DefaultNamespace'>portTypeNS:MySpringService</wsdl-port-type>
| <wsdl-binding xmlns:bindingNS='http://DefaultNamespace'>bindingNS:MySpringServiceSoapBinding</wsdl-binding>
| <service-endpoint-method-mapping>
| <java-method-name>listConfigurationName</java-method-name>
| <wsdl-operation>listConfigurationName</wsdl-operation>
| <method-param-parts-mapping>
| <param-position>0</param-position>
| <param-type>java.lang.String</param-type>
| <wsdl-message-mapping>
| <wsdl-message xmlns:wsdlMsgNS='http://DefaultNamespace'>wsdlMsgNS:listConfigurationNameRequest</wsdl-message>
| <wsdl-message-part-name>in0</wsdl-message-part-name>
| <parameter-mode>IN</parameter-mode>
| </wsdl-message-mapping>
| </method-param-parts-mapping>
| <wsdl-return-value-mapping>
| <method-return-value>DefaultNamespace.ArrayOf_tns2_anyType</method-return-value>
| <wsdl-message xmlns:wsdlMsgNS='http://DefaultNamespace'>wsdlMsgNS:listConfigurationNameResponse</wsdl-message>
| <wsdl-message-part-name>listConfigurationNameReturn</wsdl-message-part-name>
| </wsdl-return-value-mapping>
| </service-endpoint-method-mapping>
| <service-endpoint-method-mapping>
| <java-method-name>getName</java-method-name>
| <wsdl-operation>getName</wsdl-operation>
| <wsdl-return-value-mapping>
| <method-return-value>java.lang.String</method-return-value>
| <wsdl-message xmlns:wsdlMsgNS='http://DefaultNamespace'>wsdlMsgNS:getNameResponse</wsdl-message>
| <wsdl-message-part-name>getNameReturn</wsdl-message-part-name>
| </wsdl-return-value-mapping>
| </service-endpoint-method-mapping>
| <service-endpoint-method-mapping>
| <java-method-name>setName</java-method-name>
| <wsdl-operation>setName</wsdl-operation>
| <method-param-parts-mapping>
| <param-position>0</param-position>
| <param-type>java.lang.String</param-type>
| <wsdl-message-mapping>
| <wsdl-message xmlns:wsdlMsgNS='http://DefaultNamespace'>wsdlMsgNS:setNameRequest</wsdl-message>
| <wsdl-message-part-name>in0</wsdl-message-part-name>
| <parameter-mode>IN</parameter-mode>
| </wsdl-message-mapping>
| </method-param-parts-mapping>
| </service-endpoint-method-mapping>
| </service-endpoint-interface-mapping>
| </java-wsdl-mapping>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993900#3993900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993900
17 years, 5 months
[JBossWS] - Differnce in Web-Service
by subramaniam.venkat
Hello,
I have a probelm in my application.
We are where using JBoss-3.2.4 and for the deploying the web-services we used to deploy the web-service.xml and the wsdl file will be generated.
Mainly for the Exception clases we had the following wsdl generated <complexType name="SoapManagementException">
| <sequence>
|
| <element name="action" nillable="true" type="xsd:string"/>
| <element name="elementName" nillable="true" type="xsd:string"/>
| <element name="faultClass" nillable="true" type="xsd:string"/>
| <element name="reason" nillable="true" type="xsd:string"/>
| <element name="rootCause" nillable="true" type="xsd:string"/>
| </sequence>
| </complexType>
Now we have ported our application to the new JBoss-4.0.3-SP1 . The code for the exception class is same and there is no change in the web-service.xml but the generated wsdl file has changed . Now there is a extra field
<complexType name="SoapManagementException">
| <sequence>
| <element name="message" nillable="true" type="xsd:string"/>
| <element name="action" nillable="true" type="xsd:string"/>
| <element name="elementName" nillable="true" type="xsd:string"/>
| <element name="faultClass" nillable="true" type="xsd:string"/>
| <element name="reason" nillable="true" type="xsd:string"/>
| <element name="rootCause" nillable="true" type="xsd:string"/>
| </sequence>
| </complexType>
The SoapManagementException extends java.lang.Exception .
But can someone tell me why is this new field introduced when deployed in the new JBoss.
Any help we will be very helpful.
Awaiting replies,
Subramaniam V
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993762#3993762
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993762
17 years, 5 months
[JBossWS] - Needed WS4EE jars missing in JBoss4.0.5.GA
by mp123
Hello,
While I'm trying to build MedRec Application by referring some of the jar files from JBoss 4.0.5.GA, found the missing jars as follows.
Code:
axis-ws4ee.jar
jboss-ws4ee.jar
When I try to build the Application, I get the following Error.
#cd <MEDREC_HOME>/src
| #ant
| ...
| ...
| genWSjava:
| [java] Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/axis/wsdl/WSDL2Java
| [java] Java Result: 1
|
| compilewsejb:
| [javac] Compiling 14 source files to /disk1/jboss/4.0.5/demos/medrec/build/medrecEar/webServicesEjb
| [javac] /disk1/jboss/4.0.5/demos/medrec/build/medrecEar/webServicesEjb/com/bea/medrec/webservices/AddressWS.java:148: package org.jboss.axis.description does not exist
| [javac] private static org.jboss.axis.description.TypeDesc typeDesc =
| [javac] ^
|
I have found these two jars in JBoss 4.0.4.GA at the following location.
docs/examples/ws4ee/jboss-ws4ee.sar
But, the folder jboss-ws4ee.sar is not present in the latest release JBoss 4.0.5.GA.
Where can I get the above two jar files for JBoss 4.0.5.GA and what is the reason for removing it in JBoss 4.0.5.GA release??
What is the alternative method for rectifying this problem with JBoss 4.0.5.GA??
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993675#3993675
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993675
17 years, 5 months
[JBossWS] - Null pointer exception when using JBOSSWS 1.0.4 GA vesion
by ichunlin
Does anyone seen this before and what might be causing it? Thanks!
[wstools] java.lang.NullPointerException
[wstools] at java.io.File.(File.java:194)
[wstools] at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:282)
[wstools] at org.jboss.ws.tools.WSTools.process(WSTools.java:138)
[wstools] at org.jboss.ws.tools.WSTools.generate(WSTools.java:120)
[wstools] at org.jboss.ws.tools.ant.wstools.execute(wstools.java:103)
[wstools] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[wstools] at org.apache.tools.ant.Task.perform(Task.java:364)
[wstools] at org.apache.tools.ant.Target.execute(Target.java:341)
[wstools] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[wstools] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[wstools] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[wstools] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[wstools] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[wstools] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[wstools] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[wstools] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[wstools] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993650#3993650
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993650
17 years, 5 months