November 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3386) Usernametoken support requires optional elements

by Matt Wringe (Created) (JIRA)

Usernametoken support requires optional elements ------------------------------------------------ Key: JBWS-3386 URL: https://issues.jboss.org/browse/JBWS-3386 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Matt Wringe Usernametoken support is currently broken as it requires a username and password to be present in the wss security header. According to the WSS specifications (both 1.0 and 1.1*) these are optional elements in wsse:UsernameToken. If either one of these elements are missing, then JBossWS incorrectly throws a WSSecurityException. See http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk/modules/core/sr... lines 78 and 84 for where it should not be throwing this error. * 1.1 spec http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-... 1.0 spec http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-pr... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
4
0 / 0

[JBoss JIRA] (JBWS-3388) Rewrite tests using JMX to connect to the server

by Richard Opalka (Created) (JIRA)

Rewrite tests using JMX to connect to the server ------------------------------------------------ Key: JBWS-3388 URL: https://issues.jboss.org/browse/JBWS-3388 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-cxf-4.0.1, jbossws-native-4.0.1 The JMX support have been removed in AS 7.1 We need to investigate different approach and rewrite the tests relying on this feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBWS-2251) Enhance X509 certificate issuer comparison

by Alessio Soldano (JIRA)

Enhance X509 certificate issuer comparison ------------------------------------------ Key: JBWS-2251 URL: http://jira.jboss.com/jira/browse/JBWS-2251 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-native-3.0.2 Reporter: Alessio Soldano See the forum message -- 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

12 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-3262) CXF should propagate STaX parsing errors to higher levels, and not just print warning

by Richard Opalka (JIRA)

CXF should propagate STaX parsing errors to higher levels, and not just print warning ------------------------------------------------------------------------------------- Key: JBWS-3262 URL: https://issues.jboss.org/browse/JBWS-3262 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Richard Opalka Assignee: ema Fix For: jbossws-cxf-4.0 See JBWS1582TestCase FIXME -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-2858) Remove obsolete JBossWS console and provide JOPR plugin replacing it

by Richard Opalka (JIRA)

Remove obsolete JBossWS console and provide JOPR plugin replacing it -------------------------------------------------------------------- Key: JBWS-2858 URL: https://jira.jboss.org/jira/browse/JBWS-2858 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Fix For: jbossws-cxf-3.3, jbossws-metro-3.3, jbossws-native-3.3 There is legacy jbossws-console.war in deploy directory. This needs to be removed and replaced with JOPR webservices plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-3011) Make the default JAX-WS Client and Endpoint Configuration configurable

by David Boeren (JIRA)

Make the default JAX-WS Client and Endpoint Configuration configurable ---------------------------------------------------------------------- Key: JBWS-3011 URL: https://jira.jboss.org/jira/browse/JBWS-3011 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR2 Reporter: David Boeren Priority: Minor I would like to have a possibility to configure the default JAX-WS Client and Endpoint Configuration. Currently the "Standard Client" (in file "standard-jaxws-client-config.xml") and "Standard Endpoint" (in file "standard-jaxws-endpoint-config.xml") are hardcoded in the interface org.jboss.ws.metadata.config.ConfigurationProvider as default configurations. If a common enterprise specific configuration is in available then it would be nice to have the possibility to set it by default. Currently, every endpoint or client must define the annotation @EndpointConfig and @HandlerChain respectively. A possibility would be to have two system properties to define the default configuration name for clients and endpoints for a JBoss server. I think from a JBoss/JBossWS perspective it makes sense to name them something like jbossws.jaxws.default.endpoint.config and jbossws.jaxws.default.client.config By-the-way: It probably make also sense to make the default configuration filename configurable. The filename is more or less at the same place in the code. The solution could look similar as described for configuration name. However, configurable default filenames is not a requirement for me. As a test, I have patched three classes in my JBoss in order to have a possibility to set the default configuration by system property. For client configuration: - org.jboss.ws.metadata.umdm.ClientEndpointMetaData - org.jboss.ws.tools.metadata.ToolsEndpointMetaData For endpoint configuration: - org.jboss.ws.metadata.umdm.ServerEndpointMetaData For example, I have only replaced the line String configName = ConfigurationProvider.DEFAULT_ENDPOINT_CONFIG_NAME; with the following String configName = System.getProperty("jbossws.jaxws.default.endpoint.config", "AXA Standard Endpoint"); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
3
0 / 0

[JBoss JIRA] (JBWS-3392) Put schema's used in JBossWS in the docs/schema directory of JBoss for reference

by Mustafa Musaji (Created) (JIRA)

Put schema's used in JBossWS in the docs/schema directory of JBoss for reference -------------------------------------------------------------------------------- Key: JBWS-3392 URL: https://issues.jboss.org/browse/JBWS-3392 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.0 Reporter: Mustafa Musaji We would like to see the schema's used in jbossws also included in the docs/schema directory for ease of reference. This was raised in JBWS-1769 and also refused but without valid reason that I can tell. It's a legitimate request so please reconsider again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3320) JBoss Native WS - problem with Abstract class as output Parameter in WebService

by prakash pethe (JIRA)

JBoss Native WS - problem with Abstract class as output Parameter in WebService ------------------------------------------------------------------------------- Key: JBWS-3320 URL: https://issues.jboss.org/browse/JBWS-3320 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Environment: - jboss-5.1.0.GA - eclipseHelios -windowsXp- SP3 Reporter: prakash pethe I've a problem to use abstract class in a Web Service like WebMethod output parameter. I'm using JBOSS-5.1.0.GA and java runtime Version 6. It always return emtpry tag for abstract tag. I have completed below step as well When running under Java 6 you need to manually copy the following libraries from the JBOSS_HOME/client directory to the JBOSS_HOME/lib/endorsed directory, so that the JAX-WS 2.0 apis supported by JBossWS are used: jbossws-native-saaj.jar jbossws-native-jaxrpc.jar jbossws-native-jaxws.jar jbossws-native-jaxws-ext.jar for below section of WSDL: <xsd:complexType name="Personne" abstract="true" /> <xsd:complexType name="PersonnePhysique"> <xsd:complexContent> <xsd:extension base="Personne"> Getting below error stack: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException: Unable to create an instance of com.sfr.sigc.rechercherpersonneetroles.Personne - with linked exception: [java.lang.InstantiationException] at org.jboss.ws.core.jaxws.JAXBDeserializer.handleUnmarshallException(JAXBDeserializer.java:110) at org.jboss.ws.core.jaxws.JAXBDeserializer.deserialize(JAXBDeserializer.java:78) at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:58) at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:179) at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:96) at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:140) at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:85) at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:172) at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:261) at org.jboss.ws.core.EndpointInvocation.getReturnValue(EndpointInvocation.java:195) at org.jboss.ws.core.CommonClient.syncOutputParams(CommonClient.java:511) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:397) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) at $Proxy309.rechercherPersonneEtRoles(Unknown Source) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3339) Preamble is omitted when supplying external XSDs

by Kyle Lape (JIRA)

Preamble is omitted when supplying external XSDs ------------------------------------------------ Key: JBWS-3339 URL: https://issues.jboss.org/browse/JBWS-3339 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Kyle Lape The XML preamble is omitted when serving external WSDL resources. This can cause problem when specifying a non-default character set using the XML preamble. For example, you access an external XSD: http://localhost:8080/testService/Service?wsdl&resource=external.xsd The file on the server starts like this: <?xml version="1.0" encoding="UTF-8"?> <xsd:schema ...> ... </xsd:schema> But when it's served to a client, it starts like this: <xsd:schema ...> ... </xsd:schema> This affects the WSDL and any resources referenced by the WSDL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-3165) Add support for jax-ws xml catalog to be spec-compliant

by Robert Dale (JIRA)

Add support for jax-ws xml catalog to be spec-compliant ------------------------------------------------------- Key: JBWS-3165 URL: https://jira.jboss.org/browse/JBWS-3165 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Robert Dale <ropalka> rdale, OK, JAXWS 2.2 - section 4.4 <ropalka> --- <ropalka> The catalog is assembled by taking into account all accessible resources whose name is META-INF/jax- <ropalka> -ws-catalog.xml. Each resource MUST be a valid entity catalog according to the XML Catalogs 1.1 <ropalka> specification. When running on the Java SE platform, the current context class loader MUST be used to <ropalka> retrieve all the resources with the specified name. Relative URIs inside a catalog file are relative to the <ropalka> location of the catalog that contains them. <ropalka> --- <ropalka> rdale, AFAIK Native doesn't support it. It uses proprietary jbossws-entities.properties approach <ropalka> rdale, CXF should support it. <ropalka> rdale, Do U use JBossWS Native or JBossWS CXF? <darran> ropalka, CXF does, we are using it in SOA-P 5.1 <ropalka> rdale, I confirm JBossWS Native doesn't support it (although this is required by JAX-WS spec). The reason is this is not tested in TCK6 (certification suites) and we didn't have feature request to implement it yet. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2011