[JBoss JIRA] Created: (JBWS-1317) webservices.xml override does not account for namespaces
by Jason T. Greene (JIRA)
webservices.xml override does not account for namespaces
--------------------------------------------------------
Key: JBWS-1317
URL: http://jira.jboss.com/jira/browse/JBWS-1317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Jason T. Greene
Assigned To: Alejandro Guizar
Fix For: jbossws-1.0.5
I am trying to deploy multiple session ejb's as webservices. As of JBoss 1.0.3 new append flag was added to configuration:
<webservices ejb-link="BenefitsValidationService" append="true"/>
While using this flag webservices.xml is not overwritten which is exactly the behavior that I need. However, the name space is only specified for the first service. While deploying this webservice JBoss throws exception complaining about not being able to find elements in the namespace specified. Below are the configuration files that I use and the webservices.xml file that gets produced.
Address Validation (1st service) configuration:
<java-wsdl>
<namespaces target-namespace="http://edv.etenet.com/AddressValidationService"
type-namespace="http://edv.etenet.com/AddressValidationService/types"/>
<webservices ejb-link="AddressValidationService" append="true"/>
</java-wsdl>
BenefitsValidation (2nd service) configuration:
<java-wsdl>
<namespaces target-namespace="http://edv.etenet.com/BenefitsValidationService"
type-namespace="http://edv.etenet.com/BenefitsValidationService/types"/>
<webservices ejb-link="BenefitsValidationService" append="true"/>
</java-wsdl>
Resulting webservices.xml file. Please note xmlns:impl='http://edv.etenet.com/AddressValidationService' specified. JBoss Assumes that it can find BenefitsValidationService also in xmlns:impl. Wstools does not create a different namespace:
<webservices version='1.1' xmlns='http://java.sun.com/xml/ns/j2ee' xmlns:impl='http://edv.etenet.com/AddressValidationService' 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>AddressValidationService</webservice-description-name>
<wsdl-file>META-INF/wsdl/AddressValidationService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/AddressValidationService-mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>AddressValidationServiceSEIPort</port-component-name>
<wsdl-port> impl:AddressValidationServiceSEIPort </wsdl-port>
<service-endpoint-interface>com.psc.edv.avs.ejb.AddressValidationServiceSEI</service-endpoint-interface>
<service-impl-bean>
<ejb-link>AddressValidationService</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
<webservice-description>
<webservice-description-name>BenefitsValidationService</webservice-description-name>
<wsdl-file>META-INF/wsdl/BenefitsValidationService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/BenefitsValidationService-mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>BenefitsValidationServiceSEIPort</port-component-name>
<wsdl-port> impl:BenefitsValidationServiceSEIPort </wsdl-port>
<service-endpoint-interface>com.psc.edv.bvs.ejb.BenefitsValidationServiceSEI</service-endpoint-interface>
<service-impl-bean>
<ejb-link>BenefitsValidationService</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months
[JBoss JIRA] Created: (JBWS-1383) NPE when doc/lit message uses simple type in response
by Thomas Diesler (JIRA)
NPE when doc/lit message uses simple type in response
-----------------------------------------------------
Key: JBWS-1383
URL: http://jira.jboss.com/jira/browse/JBWS-1383
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxrpc
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-1.0.5
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(JSR109MetaDataBui
lder.java:580)
at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuild
er.java:200)
at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBui
lder.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:
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months
[JBoss JIRA] Created: (JBWS-1393) Problem interpreting messages with attachment when confronted with no <start> header
by Romeu Figueira (JIRA)
Problem interpreting messages with attachment when confronted with no <start> header
------------------------------------------------------------------------------------
Key: JBWS-1393
URL: http://jira.jboss.com/jira/browse/JBWS-1393
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Environment: JBoss AS 4.0.5, JBossWS 1.0.4, JDK 1.5.0.8, Windows XP SP2 and HP-UX
Reporter: Romeu Figueira
The current JBoss WS stack fails to properly interpret the MIME boundary when a message is put through without a <start> part in the MIME Headers. It skips the rootpart and gives an error of "multipart/related type specified a root type other than the one that was found." when finding the attachment part.
Using TCPMon confirms that a correct message was put out.
A fix is available in the forum thread.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months