October 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1309) Support xml overrides for @PortComponent

by Jason T. Greene (JIRA)

Support xml overrides for @PortComponent ---------------------------------------- Key: JBWS-1309 URL: http://jira.jboss.com/jira/browse/JBWS-1309 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxws Reporter: Jason T. Greene Fix For: jbossws-2.0.0 Similar to EJB3 annotations, we need to support an xml override for the PortComponent annotation. The information will then need to be pulled from the JBoss metadata. -- 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

14 years, 11 months

7
22
0 / 0

[JBoss JIRA] Created: (JBWS-1312) Fix JMS transport in trunk

by Jason T. Greene (JIRA)

Fix JMS transport in trunk -------------------------- Key: JBWS-1312 URL: http://jira.jboss.com/jira/browse/JBWS-1312 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason T. Greene Fix For: jbossws-2.0.0 -- 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, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBWS-1316) Add support for a configurable time tolerance value that handles clock skew

by Jason T. Greene (JIRA)

Add support for a configurable time tolerance value that handles clock skew --------------------------------------------------------------------------- Key: JBWS-1316 URL: http://jira.jboss.com/jira/browse/JBWS-1316 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Reporter: Jason T. Greene Fix For: jbossws-1.0.5 -- 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, 8 months

4
9
0 / 0

[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, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-1307) JAXWS user guide and sampes

by Thomas Diesler (JIRA)

JAXWS user guide and sampes --------------------------- Key: JBWS-1307 URL: http://jira.jboss.com/jira/browse/JBWS-1307 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: documentation Reporter: Thomas Diesler Fix For: jbossws-2.0.0 The user guide should cover all aspects of the JAXWS specification. Every chapter should be associated with code samples. It should be possible to take the userguide + samples and have instant working code as a easy entry point to JAXWS -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1308) JAXWS training material and labs

by Thomas Diesler (JIRA)

JAXWS training material and labs -------------------------------- Key: JBWS-1308 URL: http://jira.jboss.com/jira/browse/JBWS-1308 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: documentation Reporter: Thomas Diesler Fix For: jbossws-2.0.0 The user guide should cover all aspects of the JAXWS specification. Every chapter should be associated with code samples. It should be possible to take the userguide + samples and have instant working code as a easy entry point to JAXWS -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1304) Automatically detect Connector ports when deployed to Tomcat

by Darran Lofthouse (JIRA)

Automatically detect Connector ports when deployed to Tomcat ------------------------------------------------------------ Key: JBWS-1304 URL: http://jira.jboss.com/jira/browse/JBWS-1304 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Environment: Tomcat Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.0.5 Automatically detect Connector ports when deployed to Tomcat. JBWS-1115 adds functionality to automatically detect the connector ports when deploying to JBoss, the same should be implemented when deploying to Tomcat. -- 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

2
3
0 / 0

[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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1313) Fix XOP tests in trunk

by Jason T. Greene (JIRA)

Fix XOP tests in trunk ---------------------- Key: JBWS-1313 URL: http://jira.jboss.com/jira/browse/JBWS-1313 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-2.0.0 Reporter: Jason T. Greene Assigned To: Heiko Braun -- 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, 12 months

2
3
0 / 0

[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

18 years

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2006