[JBossWS] - bean-deployer:2.0: deployment is not bound as a global eleme
by swamini2
I am using JBoss-4.0.5 with JBossWS-2.0.0-CR1 and getting following exception while server startup:
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/space/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jbossws.beans/META-I
NF/jboss-beans.xml
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:125)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java
:106)
at org.jboss.deployment.SchemaBindingSimpleSubDeployerSupport.parseMetaD
ata(SchemaBindingSimpleSubDeployerSupport.java:51)
... 71 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {urn:jboss:bean-deployer:2.0}deployment is not bound as a global element.
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startE
lement(SundayContentHandler.java:436)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHan
dler.startElement(SaxJBossXBParser.java:269)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour
ce)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unkn
own Source)
I looked into jboss-beans.xml and could not find anything wrong.
Please help to get this issue resolved.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985186#3985186
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985186
18 years, 2 months
[JBossWS] - JBossXBException: Failed to parse source
by swamini2
I am using JBossAS4.0.5 with JBossWS1.0.3. I have followed JBossWS user guide to developed a JSR181 based web service. I started with WSDL and generated Java interface using wstools.sh. After implementing the interface, I packaged the jaxrpc-mapping.xml, application-client.xml, jboss-client.xml, web.xml, WSDL file and compiled classes into a WAR file. The deployment went fine and JBoss 4.0.5 server starts fine. I can access my webservice using a browser. However when I access it using a Java client, I get following error:
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Not supported xsdType: anyType, hashCode=-842881210
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:156)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java
:126)
at org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshall
erImpl.java:63)
... 32 more
Caused by: java.lang.IllegalStateException: Not supported xsdType: anyType, hash
Code=-842881210
at org.jboss.xb.binding.SimpleTypeBindings.unmarshal(SimpleTypeBindings.
java:940)
at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal
(CharactersHandler.java:111)
at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHa
ndler.unmarshal(RtCharactersHandler.java:64)
at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal
(CharactersHandler.java:116)
at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHa
ndler.unmarshal(RtCharactersHandler.java:64)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endEle
ment(SundayContentHandler.java:599)
> more clipboard.txt
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Not su
pported xsdType: anyType, hashCode=-842881210
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:156)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java
:126)
at org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshall
erImpl.java:63)
... 32 more
Caused by: java.lang.IllegalStateException: Not supported xsdType: anyType, hash
Code=-842881210
at org.jboss.xb.binding.SimpleTypeBindings.unmarshal(SimpleTypeBindings.
java:940)
at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal
(CharactersHandler.java:111)
at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHa
ndler.unmarshal(RtCharactersHandler.java:64)
at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal
(CharactersHandler.java:116)
at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHa
ndler.unmarshal(RtCharactersHandler.java:64)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endEle
ment(SundayContentHandler.java:599)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endEle
ment(SundayContentHandler.java:133)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHan
dler.endElement(SaxJBossXBParser.java:273)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source
)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknow
n Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Sour
ce)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:152)
... 34 more
It looks like some schema has xsd:anyType in it. However neither WSDL nor any imported schema has anyType in it.
Please help understand why this error is coming.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985182#3985182
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985182
18 years, 2 months
[JBossWS] - Mixed SOAP parameter styles not supported - migrating from 4
by bgrieder
Hello,
I am getting the following error when deploying webservices (that deploy in 4.0.2) to 4.0.5
anonymous wrote :
| org.jboss.ws.WSException: Mixed SOAP parameter styles not supported
| org.jboss.ws.metadata.EndpointMetaData.setParameterStyle(EndpointMetaData.java:224)
| org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBuilder.java:500)
| org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:200)
| org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java:223)
| org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:85)
| org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
| org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
|
The webservices are of the document/literal type. The error seems to be linked to the wsdl file but I cannot see any significant difference with various exmpales I have found.
Could you please point me to what could be the possible cause of such an error?
Thanks and Regards
Bruno
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985170#3985170
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985170
18 years, 2 months
[JBossWS] - Exception while deploying a webservice with attachment (star
by mnsharif
Hi All
I am trying to create a webservice that can receive an attachment alongwith a few other parameters. I am starting from a WSDL file and i am specifying attachments using mime content element as shown in the code below:
<definitions
| name = "Gasherbrum"
| targetNamespace = "http://org.jboss.test.webservice/samples2"
| xmlns:tns = "http://org.jboss.test.webservice/samples2"
| xmlns = "http://schemas.xmlsoap.org/wsdl/"
| xmlns:ns2 = "http://org.jboss.test.webservice/samples2/types"
| xmlns:mime = "http://schemas.xmlsoap.org/wsdl/mime/"
| xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
| xmlns:soap = "http://schemas.xmlsoap.org/wsdl/soap/">
| <types>
| <schema
| targetNamespace = "http://org.jboss.test.webservice/samples2/types"
| xmlns:tns = "http://org.jboss.test.webservice/samples2/types"
| xmlns:soap11-enc = "http://schemas.xmlsoap.org/soap/encoding/"
| xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
| xmlns:wsdl = "http://schemas.xmlsoap.org/wsdl/"
| xmlns = "http://www.w3.org/2001/XMLSchema">
| <complexType name = "paraListType">
| <sequence>
| <element
| name = "username"
| type = "string"
| nillable = "true"/>
| <element
| name = "password"
| type = "string"
| nillable = "true"/>
| <element
| name = "operationName"
| type = "string"
| nillable = "true"/>
| <element
| name = "inputXML"
| type = "string"
| nillable = "true"/>
| </sequence>
| </complexType>
| <complexType name = "responseType">
| <sequence>
| <element
| name = "result"
| type = "string"
| nillable = "true"/>
| </sequence>
| </complexType>
| <element name = "paraList2" type = "tns:paraListType"/>
| <element name = "responseXML" type = "tns:responseType"/>
| </schema>
| </types>
| <message name = "attachRequest">
| <part name = "parameters" element = "ns2:paraList2"/>
| <part name = "attachmentContents" type = "xsd:string"/>
| </message>
| <message name = "attachResponse">
| <part name = "result" element = "ns2:responseXML"/>
| </message>
| <portType name = "TransmulatorInterface">
| <operation name = "invokeAttach">
| <input message = "tns:attachRequest"/>
| <output message = "tns:attachResponse"/>
| </operation>
| </portType>
| <binding name = "TransmulatorInterfaceBinding" type = "tns:TransmulatorInterface">
| <soap:binding transport = "http://schemas.xmlsoap.org/soap/http" style = "document"/>
| <operation name = "invokeAttach">
| <input>
| <mime:multipartRelated>
| <mime:part>
| <soap:body use = "literal"/>
| </mime:part>
| <mime:part>
| <mime:content part = "attachmentContents" type = "text/plain"/>
| </mime:part>
| </mime:multipartRelated>
| </input>
| <output>
| <mime:multipartRelated>
| <mime:part>
| <soap:body use = "literal"/>
| </mime:part>
| </mime:multipartRelated>
| </output>
| </operation>
| </binding>
| <service name = "Gasherbrum">
| <port name = "TransmulatorInterfacePort" binding = "tns:TransmulatorInterfaceBinding">
| <soap:address location = "REPLACE_WITH_ACTUAL_URL"/>
| </port>
| </service>
| </definitions>
|
This WSDL generates SEI without any problems and get deploed easily on tomcat using JWSDP1.6, but when i tried the same WSDL file and tried to generate SEI through wscmopile and tried to deploy on JBoss, i get the following deployment exception:
22:11:09,354 WARN [JavaWsdlMapping] Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XMLSchema}string
| 22:11:09,354 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss-4.0.4.GA/server/default/deploy/alhamd.war
| org.jboss.ws.WSException: Cannot obtain java/xml type mapping for: {http://www.w3.org/2001/XMLSchema}string
| at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBuilder.java:513)
| at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:200)
| at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java:223)
| at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:78)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
| at org.jboss.ws.integration.jboss.DeployerInterceptorJSE.create(DeployerInterceptorJSE.java:74)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.jav
| a: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 $Proxy31.create(Unknown Source)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
| at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| 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 $Proxy8.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:26
| 3)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
|
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
|
I cant seem to figure out what the problem is!
Is it that attachments are not supported in JBoss (i am using 4.0.4 with jbossws as add-on)?? or are they not supported when starting from WSDL file? Or am i ignoring something here?
Any clues in this regard would be highly appreciated.
Regards,
mnsharif
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985159#3985159
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985159
18 years, 2 months
[JBossWS] - deployment exception for document based webservice
by mnsharif
Hi all!
I am using a document style web service (starting from WSDL) and i have complex data types defined in the WSDL. My WSDL file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
| <definitions
| name = "Gasherbrum"
| targetNamespace = "http://bla.bla.com/targetNamespace"
| xmlns:tns = "http://bla.bla.com/targetNamespace"
| xmlns:mime = "http://schemas.xmlsoap.org/wsdl/mime/"
| xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
| xmlns = "http://schemas.xmlsoap.org/wsdl/"
| xmlns:ns2 = "http://bla.bla.com/typeNamespace"
| xmlns:soap = "http://schemas.xmlsoap.org/wsdl/soap/">
| <types>
| <schema
| targetNamespace = "http://bla.bla.com/typeNamespace"
| xmlns:tns = "http://bla.bla.com/typeNamespace"
| xmlns:soap11-enc = "http://schemas.xmlsoap.org/soap/encoding/"
| xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
| xmlns:wsdl = "http://schemas.xmlsoap.org/wsdl/"
| xmlns = "http://www.w3.org/2001/XMLSchema">
| <complexType name = "paraListType">
| <sequence>
| <element
| name = "username"
| type = "string"
| nillable = "false"/>
| <element
| name = "password"
| type = "string"
| nillable = "false"/>
| <element
| name = "operationName"
| type = "string"
| nillable = "false"/>
| <element
| name = "inputXML"
| type = "string"
| nillable = "false"/>
| </sequence>
| </complexType>
| <element name = "paraList1" type = "tns:paraListType"/>
| <element name = "responseXML" type = "xsd:string"/>
| </schema>
| </types>
| <message name = "invokeRequest">
| <part name = "parameters" element = "ns2:paraList1"/>
| </message>
| <message name = "invokeResponse">
| <part name = "result" element = "ns2:responseXML"/>
| </message>
| <portType name = "TransmulatorInterface">
| <operation name = "invoke">
| <input message = "tns:invokeRequest"/>
| <output message = "tns:invokeResponse"/>
| </operation>
| </portType>
| <binding name = "TransmulatorInterfaceBinding" type = "tns:TransmulatorInterface">
| <soap:binding transport = "http://schemas.xmlsoap.org/soap/http" style = "document"/>
| <operation name = "invoke">
| <soap:operation soapAction = ""/>
| <input>
| <soap:body use = "literal"/>
| </input>
| <output>
| <soap:body use = "literal"/>
| </output>
| </operation>
| </binding>
| <service name = "Gasherbrum">
| <port name = "TransmulatorInterfacePort" binding = "tns:TransmulatorInterfaceBinding">
| <soap:address location = "REPLACE_WITH_ACTUAL_URL"/>
| </port>
| </service>
| </definitions>
|
I am using this WSDL file to generate service endpoint interface through wscompile tool provided by JWSDP1.6. The webservices.xml file (hand coded) is as follows:
<webservices
| version = "1.1"
| xmlns = "http://java.sun.com/xml/ns/j2ee"
| xmlns:impl = "http://bla.bla.com/targetNamespace"
| 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_web_services_1_1.xsd">
| <webservice-description>
| <webservice-description-name>Gasherbrum</webservice-description-name>
| <wsdl-file>WEB-INF/wsdl/Gasherbrum.wsdl</wsdl-file>
| <jaxrpc-mapping-file>WEB-INF/jaxrpc-mapping.xml</jaxrpc-mapping-file>
| <port-component>
| <port-component-name>TransmulatorInterfacePort</port-component-name>
| <wsdl-port>impl:TransmulatorInterfacePort</wsdl-port>
| <service-endpoint-interface>bla.bla.wsTry.TransmulatorInterface</service-endpoint-interface>
| <service-impl-bean>
| <servlet-link>path1Name</servlet-link>
| </service-impl-bean>
| </port-component>
| </webservice-description>
| </webservices>
|
Now, when i package and deploy this on my jboss installation (4.0.4 with jbossws), i get the following deployment exception:
16:41:13,233 WARN [JavaWsdlMapping] Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XMLSchema}string
| 16:41:13,233 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss-4.0.4.GA/server/default/deploy/fwExperimenting.war
| java.lang.NullPointerException
| at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBuilder.java:580)
| at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:200)
| at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java:223)
| at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:78)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
| at org.jboss.ws.integration.jboss.DeployerInterceptorJSE.create(DeployerInterceptorJSE.java:74)
| 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 $Proxy31.create(Unknown Source)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
| at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| 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 $Proxy8.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
|
|
and i am going crazy in figuring out what is wrong here. I am using the same WSDL file with tomcat+JWSDP and everything is working fine.
Please somebody point out what mistake i am doing here. It would really be a great help for me
mnsharif
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985135#3985135
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985135
18 years, 2 months
[JBossWS] - getInitParameter
by dsteinbrunn
I'm running jbossws in standalone tomcat, version 5.5.20.
I have an endpoint that extends ServiceLifecycle. I can see from my logs that init is being called and I have access to ServletEndpointContext.
I have a configuration parameter I'm storing in my web.xml for the web service:
| <servlet>
| <servlet-name>MyServiceEndpoint</servlet-name>
| <servlet-class>org.service.MyServiceEndpoint</servlet-class>
| <init-param>
| <param-name>foo</param-name>
| <param-value>bar</param-value>
| </init-param>
| </servlet>
|
I try to access this in MyServiceEndpoint:
| String paramValue = this.getEndpointContext().getServletContext().getInitParameter(foo);
|
but I get nothing.
I noticed that when my service is deployed another initparam is added called ServiceEndpointImpl, which is set to the name of my SEI. I also cannot access this value from within my service.
Has anyone else encountered this issue? It's weird that I'm not seeing any of the init-params, not just the ones I added.
Thanks in advance for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985013#3985013
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985013
18 years, 2 months