[JBossWS] - WS methods with same name in different WS classes => unexpec
by samyers
Hi, I'm new to JbossWS and getting unexpected generated WSDLs from my simple test WebService classes when the classes (deployed in the same WAR) share common WebMethod names. I'm using JBossWS native version 3.0.4.GA in jboss-5.0.0.GA-jdk6.
In both WebService classes there are two methods, methodOne and methodTwo. In the TestOneWeb class both methods return Integers, in the TestTwoWeb class both methods return Strings. The WSDL for TestOneWeb looks fine, but in the WSDL for TestTwoWeb both method return ints when they should return strings.
Any help or suggestions are appreciated.
-- Steve
TestOneWeb.java:
| package com.ep.ff.web.endpoint.test;
|
| import javax.jws.WebMethod;
| import javax.jws.WebService;
|
| import org.apache.log4j.Logger;
|
| @WebService
| public class TestOneWeb
| {
| private static Logger logger = Logger.getLogger(TestOneWeb.class);
|
| @WebMethod
| public Integer methodOne(String number)
| {
| return new Integer(number);
| }
|
| @WebMethod
| public Integer methodTwo(String number)
| {
| return new Integer(number);
| }
| }
|
TestTwoWeb.java:
| package com.ep.ff.web.endpoint.test;
|
| import javax.jws.WebMethod;
| import javax.jws.WebService;
|
| import org.apache.log4j.Logger;
|
| @WebService
| public class TestTwoWeb
| {
| private static Logger logger = Logger.getLogger(TestTwoWeb.class);
|
| @WebMethod
| public String methodOne(String number)
| {
| return number;
| }
|
| @WebMethod
| public String methodTwo(String number)
| {
| return number;
| }
| }
|
web.xml:
| <?xml version="1.0" encoding="UTF-8"?>
| <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
| version="2.5">
|
| <display-name>web-test</display-name>
|
| <servlet>
| <servlet-name>TestOneWeb</servlet-name>
| <servlet-class>com.ep.ff.web.endpoint.test.TestOneWeb</servlet-class>
| </servlet>
| <servlet-mapping>
| <servlet-name>TestOneWeb</servlet-name>
| <url-pattern>/ws/TestOne</url-pattern>
| </servlet-mapping>
|
| <servlet>
| <servlet-name>TestTwoWeb</servlet-name>
| <servlet-class>com.ep.ff.web.endpoint.test.TestTwoWeb</servlet-class>
| </servlet>
| <servlet-mapping>
| <servlet-name>TestTwoWeb</servlet-name>
| <url-pattern>/ws/TestTwo</url-pattern>
| </servlet-mapping>
| </web-app>
|
http://localhost:8080/web-test/ws/TestOne?wsdl :
| <definitions name="TestOneWebService" targetNamespace="http://test.endpoint.web.ff.ep.com/"
| xmlns="http://schemas.xmlsoap.org/wsdl/"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| xmlns:tns="http://test.endpoint.web.ff.ep.com/"
| xmlns:xsd="http://www.w3.org/2001/XMLSchema">
| <types>
| <xs:schema targetNamespace="http://test.endpoint.web.ff.ep.com/"
| version="1.0" xmlns:tns="http://test.endpoint.web.ff.ep.com/"
| xmlns:xs="http://www.w3.org/2001/XMLSchema">
| <xs:element name="methodOne" type="tns:methodOne"/>
| <xs:element name="methodOneResponse" type="tns:methodOneResponse"/>
| <xs:element name="methodTwo" type="tns:methodTwo"/>
| <xs:element name="methodTwoResponse" type="tns:methodTwoResponse"/>
| <xs:complexType name="methodOne">
| <xs:sequence>
| <xs:element minOccurs="0" name="arg0" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="methodOneResponse">
| <xs:sequence>
| <xs:element minOccurs="0" name="return" type="xs:int"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="methodTwo">
| <xs:sequence>
| <xs:element minOccurs="0" name="arg0" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="methodTwoResponse">
| <xs:sequence>
| <xs:element minOccurs="0" name="return" type="xs:int"/>
| </xs:sequence>
| </xs:complexType>
| </xs:schema>
| </types>
| <message name="TestOneWeb_methodOne">
| <part element="tns:methodOne" name="methodOne"/>
| </message>
| <message name="TestOneWeb_methodTwo">
| <part element="tns:methodTwo" name="methodTwo"/>
| </message>
| <message name="TestOneWeb_methodOneResponse">
| <part element="tns:methodOneResponse" name="methodOneResponse"/>
| </message>
| <message name="TestOneWeb_methodTwoResponse">
| <part element="tns:methodTwoResponse" name="methodTwoResponse"/>
| </message>
| <portType name="TestOneWeb">
| <operation name="methodOne" parameterOrder="methodOne">
| <input message="tns:TestOneWeb_methodOne"/>
| <output message="tns:TestOneWeb_methodOneResponse"/>
| </operation>
| <operation name="methodTwo" parameterOrder="methodTwo">
| <input message="tns:TestOneWeb_methodTwo"/>
| <output message="tns:TestOneWeb_methodTwoResponse"/>
| </operation>
| </portType>
| <binding name="TestOneWebBinding" type="tns:TestOneWeb">
| <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
| <operation name="methodOne">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal"/>
| </input>
| <output>
| <soap:body use="literal"/>
| </output>
| </operation>
| <operation name="methodTwo">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal"/>
| </input>
| <output>
| <soap:body use="literal"/>
| </output>
| </operation>
| </binding>
| <service name="TestOneWebService">
| <port binding="tns:TestOneWebBinding" name="TestOneWebPort">
| <soap:address location="http://localhost:8080/web-test/ws/TestOne"/>
| </port>
| </service>
| </definitions>
|
http://localhost:8080/web-test/ws/TestTwo?wsdl :
| <definitions name="TestTwoWebService" targetNamespace="http://test.endpoint.web.ff.ep.com/"
| xmlns="http://schemas.xmlsoap.org/wsdl/"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| xmlns:tns="http://test.endpoint.web.ff.ep.com/"
| xmlns:xsd="http://www.w3.org/2001/XMLSchema">
| <types>
| <xs:schema targetNamespace="http://test.endpoint.web.ff.ep.com/"
| version="1.0" xmlns:tns="http://test.endpoint.web.ff.ep.com/"
| xmlns:xs="http://www.w3.org/2001/XMLSchema">
| <xs:element name="methodOne" type="tns:methodOne"/>
| <xs:element name="methodOneResponse" type="tns:methodOneResponse"/>
| <xs:element name="methodTwo" type="tns:methodTwo"/>
| <xs:element name="methodTwoResponse" type="tns:methodTwoResponse"/>
| <xs:complexType name="methodOne">
| <xs:sequence>
| <xs:element minOccurs="0" name="arg0" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="methodOneResponse">
| <xs:sequence>
| <xs:element minOccurs="0" name="return" type="xs:int"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="methodTwo">
| <xs:sequence>
| <xs:element minOccurs="0" name="arg0" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="methodTwoResponse">
| <xs:sequence>
| <xs:element minOccurs="0" name="return" type="xs:int"/>
| </xs:sequence>
| </xs:complexType>
| </xs:schema>
| </types>
| <message name="TestTwoWeb_methodOne">
| <part element="tns:methodOne" name="methodOne"/>
| </message>
| <message name="TestTwoWeb_methodOneResponse">
| <part element="tns:methodOneResponse" name="methodOneResponse"/>
| </message>
| <message name="TestTwoWeb_methodTwo">
| <part element="tns:methodTwo" name="methodTwo"/>
| </message>
| <message name="TestTwoWeb_methodTwoResponse">
| <part element="tns:methodTwoResponse" name="methodTwoResponse"/>
| </message>
| <portType name="TestTwoWeb">
| <operation name="methodOne" parameterOrder="methodOne">
| <input message="tns:TestTwoWeb_methodOne"/>
| <output message="tns:TestTwoWeb_methodOneResponse"/>
| </operation>
| <operation name="methodTwo" parameterOrder="methodTwo">
| <input message="tns:TestTwoWeb_methodTwo"/>
| <output message="tns:TestTwoWeb_methodTwoResponse"/>
| </operation>
| </portType>
| <binding name="TestTwoWebBinding" type="tns:TestTwoWeb">
| <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
| <operation name="methodOne">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal"/>
| </input>
| <output>
| <soap:body use="literal"/>
| </output>
| </operation>
| <operation name="methodTwo">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal"/>
| </input>
| <output>
| <soap:body use="literal"/>
| </output>
| </operation>
| </binding>
| <service name="TestTwoWebService">
| <port binding="tns:TestTwoWebBinding" name="TestTwoWebPort">
| <soap:address location="http://localhost:8080/web-test/ws/TestTwo"/>
| </port>
| </service>
| </definitions>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211253#4211253
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211253
15 years, 2 months
[JBossWS] - Accessing <entry> from SOAP Handler
by gang.yang
Hi,
I'm trying to develop a generic SOAP handler that can be configured to use with different WebService services. I need to pass into the handler service specific config data, such as config file name.
I tried to configure this generic handler with a Web-based WS service and defined the in web.xml. Even though I was not able to inject field into the handler class, I WAS able to look it up using JNDI.
However, I could not do this with an EJB3-based WS service. I defined the in ejb-jar.xml. But I could not inject the field into the handler or the EJB bean itelf. Nor could I look it up using JNDI. I'm using JBoss 4.2.2 and I could not even see the resource in the JNDIView.
Is this a bug? Does anyone have any more info or experience in this area?
Thanks,
Gang
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211249#4211249
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211249
15 years, 2 months
[JBossWS] - Using Lists of String in WSDL-first JaxWS service
by adinn
I am developing a JaxWS-based test service which supports scripting of various actions in the server. So, the service provides a single WebMethod which takes a list of command strings and returns a list of result strings. I defined this using the following WSDL:
| <definitions
| targetNamespace="http://jbossts.jboss.org/xts/servicetests/generated"
| xmlns:s="http://www.w3.org/2001/XMLSchema"
| xmlns:tns="http://jbossts.jboss.org/xts/servicetests/generated"
| xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| xmlns:wsaw="http://www.w3.org/2006/02/addressing/wsdl"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| xmlns="http://schemas.xmlsoap.org/wsdl/" >
| <types>
| <s:schema
| targetNamespace="http://jbossts.jboss.org/xts/servicetests/generated"
| xmlns="http://jbossts.jboss.org/xts/servicetests/generated">
| <s:simpleType name="commandList">
| <s:list itemType="s:string"/>
| </s:simpleType>
|
| <s:simpleType name="resultList">
| <s:list itemType="s:string">
| </s:list>
| </s:simpleType>
|
| <s:complexType name="commandsType">
| <s:sequence>
| <s:element name="commandList" type="commandList"/>
| </s:sequence>
| </s:complexType>
|
| <s:complexType name="resultsType">
| <s:sequence>
| <s:element name="resultList" type="resultList"/>
| </s:sequence>
| </s:complexType>
|
| <s:element name="commands" type="commandsType"/>
|
| <s:element name="results" type="resultsType"/>
|
| <!--
| <s:import namespace="http://schemas.xmlsoap.org/soap/envelope/"
| schemaLocation="http://schemas.xmlsoap.org/soap/envelope"/>
| -->
| </s:schema>
| </types>
|
| <message name="Commands">
| <part name="commands" element="tns:commands" />
| </message>
|
| <message name="Results">
| <part name="results" element="tns:results" />
| </message>
|
| <portType name="XTSServiceTestPortType">
| <operation name="serve">
| <input name="Commands" message="tns:Commands" />
| <output name="Results" message="tns:Results" />
| </operation>
| </portType>
|
| <binding name="XTSServiceTestPort_SOAPBinding" type="tns:XTSServiceTestPortType">
| <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
| <operation name="serve">
| <input message="tns:Commands">
| <soap:body use="literal"/>
| </input>
| <output message="tns:Commands">
| <soap:body use="literal"/>
| </output>
| </operation>
| </binding>
|
| <service name="XTSServiceTestService">
| <port binding="tns:XTSServiceTestPort_SOAPBinding" name="XTSServiceTestPortType">
| <wsaw:UsingAddressing required="true"/>
| <soap:address location="http://localhost:9000/xtsservicetests/XTSServiceTestService"/>
| </port>
| </service>
| </definitions>
|
I generated the Java code from this and obtained the following types
| @XmlAccessorType(XmlAccessType.FIELD)
| @XmlType(name = "commandsType", propOrder = {
| "commandList"
| })
| public class CommandsType {
| @XmlList
| @XmlElement(required = true)
| protected List<String> commandList;
| public List<String> getCommandList() {
| if (commandList == null) {
| commandList = new ArrayList<String>();
| }
| return this.commandList;
| }
| }
|
| @XmlAccessorType(XmlAccessType.FIELD)
| @XmlType(name = "resultsType", propOrder = {
| "resultList"
| })
| public class ResultsType {
| @XmlList
| @XmlElement(required = true)
| protected List<String> resultList;
| public List<String> getResultList() {
| if (resultList == null) {
| resultList = new ArrayList<String>();
| }
| return this.resultList;
| }
| }
|
The server interface was generated as follows:
| @WebService(name = "XTSServiceTestPortType", targetNamespace = "http://jbossts.jboss.org/xts/servicetests/generated")
| @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
| public interface XTSServiceTestPortType {
| @WebMethod
| @WebResult(name = "results", targetNamespace = "http://jbossts.jboss.org/xts/servicetests/generated", partName = "results")
| public ResultsType serve(
| @WebParam(name = "commands", targetNamespace = "http://jbossts.jboss.org/xts/servicetests/generated", partName = "commands")
| CommandsType commands);
| }
|
This works fine for a whole load of cases where I supply a series of string commands and get one or more strings as a reply. However, I found to my surprise a case where the results gets mangled. One of my command types contains the single command "subtransaction" which causes the server to start a subordinate transaction and return a transaction id. I call it as follows
| commands = new CommandsType();
| commands.getCommandList().add("subtransaction");
|
| try {
| results = port.serve(commands);
| } catch (Exception e) {
| exception = e;
| }
|
On the server side I obtain a CommandsType containing a list with the single String element "subtransaction" as expected. The code which returns the result is as follows:
| result = new ResultsType();
| resultsList = result.getResultsList()
| String id = newTx.toString();
| resultsList.add(id);
| return resultsList;
|
When I look at resultsList it contains a single String soemthing like this "AtomicTransactionIdentifier: urn:-53ef7d93:9592:499c0a00:ec".
Now, going back to the client the value returned from the call to port.serve(commands) is a ResultsType whose ResultsList contains two strings,
"AtomicTransactionIdentifier:" and "urn:-53ef7d93:9592".
In my debugger I stepped up out of the server implementation method from the return statement up to the point where the returned value was encoded into a SOAPMessage and printed the message to System.out. The result was as follows:
| 13:54:22,795 INFO [STDOUT] <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body><ns1:results xmlns:ns1="http://jbossts.jboss.org/xts/servicetests/generated"><resultList>AtomicTransactionIdentifier: urn:-53ef7d93:9592:499c0a00:ec</resultList></ns1:results></env:Body></env:Envelope>
|
It looks like the message text representation of the SOAP element corresponding to field resultsList of type List is encoded by printing the text of each String separated by spaces inside tags and decoded by reading back in the space-separated character sequences found between these tags. This appears to ignore the presence of spaces embedded in any of the Strings. That's not exactly what I would call robust :-).
Firstly, is this a WS issue or a JaxB issue?
Secondly, can I get round this by using a more sophiisticated schema or do I have to resort to registering my own encode/decode callbacks with JaxB?
I realise I could avoid the problem by making sure my Strings don't contain spaces but I'd prefer to implement a more usable service.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211101#4211101
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211101
15 years, 2 months
[JBossWS] - Re: jbossws-metro-3.0.5.GA Installer Bug
by ericcart
It've already tried it. It fails with several:
07:24:12,477 ERROR [MainDeployer] Could not create deployment: file:/home/anibal/05_bin/jbdevstudio/jboss-eap/jboss-as/server/production/deploy/httpha-invoker.sar/invoker.war/
java.lang.NoSuchMethodError: org.jboss.metadata.WebMetaData.getServletParams(Ljava/lang/String;)Ljava/util/Map;
at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.getEndpointBeans(JAXWSDeployerHookPreJSE.java:133)
at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.isWebServiceDeployment(JAXWSDeployerHookPreJSE.java:103)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:85)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:77)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy46.create(Unknown Source)
So, I downgraded 'til 422.
Thanks,
Eric
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210625#4210625
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210625
15 years, 2 months
[JBossWS] - Error installing WebService in JAXRPCMetaDataBuilder
by deberlin
Hello!
We have a web service ejb2.1 with ejb endpoint running on JBoss5.0.0.GA with JBossWS 3.0.5.GA and JDK 1.6. On JBoss 4.x works fine.
The web service artifacts generated with jwsdp-1.6.
The following error occurs:
16:48:10,706 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: vfszip:/D:/jboss5/server/default/deploy/270
| Med.jar/META-INF/wsdl/medws.xsd
| 16:48:10,753 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: vfszip:/D:/jboss5/server/default/deploy/270
| Med.jar/META-INF/wsdl/ws.xsd
| 16:48:10,862 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: vfszip:/D:/jboss5/server/default/deploy/270
| Med.jar/META-INF/wsdl/medws.xsd
| 16:48:10,925 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: vfszip:/D:/jboss5/server/default/deploy/270
| Med.jar/META-INF/wsdl/ws.xsd
| 16:48:11,112 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/D:/jboss5/server/default/deploy/270Med.jar st
| ate=PreReal mode=Manual requiredState=Real
| org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/D:/jboss5/server/default/deploy/270Med.jar
| at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
| at org.jboss.Main.boot(Main.java:209)
| at org.jboss.Main$1.run(Main.java:547)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: java.lang.IllegalArgumentException: Could not determine variable name for element: result
| at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.processOutputDocElement(JAXRPCMetaDataBuilder.java:801)
| at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildParameterMetaDataDoc(JAXRPCMetaDataBuilder.java:898)
| at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.setupOperationsFromWSDL(JAXRPCMetaDataBuilder.java:212)
| at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buildMetaData(JAXRPCServerMetaDataBuilder.java:218)
| at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:59)
| at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129)
| at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:75)
| at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60)
| at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:112)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| ... 18 more
The webservice.xml:
<?xml version="1.0" encoding="UTF-8"?>
|
| <webservices
| xmlns="http://java.sun.com/xml/ns/j2ee"
| xmlns:impl="http://www.gsd.de/amasys/server/modules/med"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
| http://java.sun.com/xml/ns/j2ee/j2ee_web_services_1_1.xsd"
| version="1.1">
|
| <webservice-description>
| <webservice-description-name>MEDWSService</webservice-description-name>
| <wsdl-file>META-INF/wsdl/medws.wsdl</wsdl-file>
| <jaxrpc-mapping-file>META-INF/server-mapping.xml</jaxrpc-mapping-file>
| <port-component>
| <port-component-name>MEDWSServicePort</port-component-name>
| <wsdl-port>impl:MEDWSServicePort</wsdl-port>
| <service-endpoint-interface>de.gsd.amasys.server.modules.med.ws.MEDWSService</service-endpoint-interface>
| <service-impl-bean>
| <ejb-link>MEDWS</ejb-link>
| </service-impl-bean>
| </port-component>
| </webservice-description>
|
| </webservices>
The ejb-jar.xml:
<?xml version = '1.0' encoding = 'windows-1252'?>
| <ejb-jar 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://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" version="2.1">
| <enterprise-beans>
|
| <session>
| <description>MEDWS</description>
| <ejb-name>MEDWS</ejb-name>
| <home>de.gsd.amasys.server.modules.med.sessions.MEDWSHome</home>
| <remote>de.gsd.amasys.server.modules.med.sessions.MEDWSRemote</remote>
| <service-endpoint>de.gsd.amasys.server.modules.med.ws.MEDWSService</service-endpoint>
| <ejb-class>de.gsd.amasys.server.modules.med.sessions.MEDWSBean</ejb-class>
| <session-type>Stateless</session-type>
| <transaction-type>Container</transaction-type>
| <resource-ref>
| <description>SAP DB Datenbank</description>
| <res-ref-name>jdbc/SAPDBDS</res-ref-name>
| <res-type>javax.sql.DataSource</res-type>
| <res-auth>Container</res-auth>
| </resource-ref>
| </session>
|
| </enterprise-beans>
| </ejb-jar>
|
The jboss.xml:
<?xml version="1.0" encoding="UTF-8"?>
|
| <jboss>
|
| <enterprise-beans>
|
| <session>
| <ejb-name>MEDWS</ejb-name>
| <jndi-name>Med/MEDWS</jndi-name>
| <local-jndi-name>Med/MEDWSLocal</local-jndi-name>
| <port-component>
| <port-component-name>MEDWSServicePort</port-component-name>
| <port-component-uri>/wsmed/MEDWSServicePort</port-component-uri>
| </port-component>
| <resource-ref>
| <res-ref-name>jdbc/SAPDBDS</res-ref-name>
| <jndi-name>java:/SAPDBDS</jndi-name>
| </resource-ref>
| </session>
|
| </enterprise-beans>
| </jboss>
|
The META-INF contains:
META-INF/wsdl/medws.wsdl
| META-INF/wsdl/medws.xsd
| META-INF/wsdl/ws.xsd
| META-INF/ejb-jar.xml
| META-INF/jboss.xml
| META-INF/server-mapping.xml <- generated JAXB file
| META-INF/webservice.xml
|
Any help would be appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210597#4210597
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210597
15 years, 2 months