[JBoss JIRA] Created: (JBWS-1314) Precursor to streaming optimizations, elimination of xmlFragment
by Thomas Diesler (JIRA)
Precursor to streaming optimizations, elimination of xmlFragment
----------------------------------------------------------------
Key: JBWS-1314
URL: http://jira.jboss.com/jira/browse/JBWS-1314
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: Thomas Diesler
Fix For: jbossws-2.0.1
At some point, we should remove the xml string fragment processing phase. It's not needed in our long term streaming optimization plan, and it adds unneeded performance overhead in the current design.
Instead we could pass the corresponding DOM chunk directly to the marshalling layer. JAXB supports this using javax.xml.transform.Source, and it wouldn't be difficult to enhance JBossXB to do the same. This would also be more robust because it would eliminate the xml escape processing that we duplicate from a standard XML parser (see [JBWS-1240] for an example).
--
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
16 years, 10 months
[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-1310) OperationMetaData.getJavaMethod throws WSException: Ambiguous javaMethod
by Ray Tomlinson (JIRA)
OperationMetaData.getJavaMethod throws WSException: Ambiguous javaMethod
------------------------------------------------------------------------
Key: JBWS-1310
URL: http://jira.jboss.com/jira/browse/JBWS-1310
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.3
Environment: Windows XP dual core processor
Reporter: Ray Tomlinson
Priority: Blocker
Running two copies of a test client beating up on a few web-service methods produces "Ambiguous javaMethod: <method>" from org.jboss.ws.metadata.OperationMetaData(getJavaMethod) (line 203). There is no potential ambiguity since all methods have quite distinctive signatures and the problem is sporadic.
I believe this a lack of synchronization between multiple threads simultaneously trying to resolve the javaMethod field. Both see that javaMethod has not yet been set and the second to finish finds the javaMethod field has already been set by the first and mis-interprets this as an ambiguous method situation. Running a dual core processor exacerbates the problem.
Cannot use jboss with this bug.
--
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, 11 months