April 2011 - jbossws-issues - Jboss List Archives

[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] 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

[JBoss JIRA] Created: (JBWS-3281) Create a migration guide to JBossWS 4.0 / AS 7 integration

by Alessio Soldano (JIRA)

Create a migration guide to JBossWS 4.0 / AS 7 integration ---------------------------------------------------------- Key: JBWS-3281 URL: https://issues.jboss.org/browse/JBWS-3281 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native, productization Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 A migration guide from JBossWS 3.4.x to JBossWS 4.0 (and in particular to AS7 w/ JBossWS 4) should be included in the release documentation. At the moment the topic to be covered should be: - consequences for users due to changes in classloading (see JBossWS AS7 FAQ) - changes in API (new jbossws-api library, package refactorings, etc.) - changes in WS-* configuration - changes due to libraries upgrades (mainly due to dependencies coming from Apache CXF 2.4 upgrade) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBWS-3255) Unable to lookup AuthenticationManager

by Richard Opalka (JIRA)

Unable to lookup AuthenticationManager -------------------------------------- Key: JBWS-3255 URL: https://issues.jboss.org/browse/JBWS-3255 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable to lookup AuthenticationManager at org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53) [jbossws-common.jar:2.0.0-SNAPSHOT] at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87) [jbossws-common.jar:2.0.0-SNAPSHOT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context '' at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20] at org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80) [jbossws-native-core.jar:4.0.0-SNAPSHOT] ... 28 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBWS-3176) JbossWS native client handler issue

by Gary Brown (JIRA)

JbossWS native client handler issue ----------------------------------- Key: JBWS-3176 URL: https://jira.jboss.org/browse/JBWS-3176 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Environment: RiftSaw 2.2.0.CR1, JBossAS 5.1.0.GA, JBossWS 3.2.2.GA (installed as part of the RiftSaw installation), JBossESB 4.9, JDK6, Savara 1.1.0.CR1 Reporter: Gary Brown I have a BPEL process that invokes two JAX-WS services, one after the other. The first invocation does not trigger the client handler configured in the 'standard-jaxws-client-config.xml' file, however the second invocation does. In terms of the environment, when you have a clean JBossAS environment, install the ESB, install Riftsaw using "ant deploy -Ddatabase=hsql -Dws.version=3.2.2.GA" (which will install jbossws native 3.2.2.GA). For now don't worry about installing Savara, as it is only configuring the client handler. May be easier for you to use your own handler, rather than installing yet another project - although if you have problems reproducing the issue, then may need to install Savara in case that is the problem. Attached are the various artifacts that need to be deployed into the server's deploy folder. The policy-quote-queue-service.xml will need to be deployed first. SoapUI can be used to send the following messages. The instructions for running the example are: 1) Send <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pol="http://www.example.org/policyQuote"> <soapenv:Header/> <soapenv:Body> <pol:policyQuote> <pol:receivePolicyQuote> <pol:requestDate>2009-01-01</pol:requestDate> <pol:task>receivePolicyQuote</pol:task> <pol:policyQuoteInfo> <pol:policyType>AUTO</pol:policyType> <pol:vehicleYear>2004</pol:vehicleYear> <pol:driverName>Bill Smith</pol:driverName> <pol:ssn>412345678</pol:ssn> <pol:dlNumber>987654321</pol:dlNumber> <pol:age>30</pol:age> <pol:numberOfAccidents>0</pol:numberOfAccidents> <pol:numberOfTickets>0</pol:numberOfTickets> <pol:creditScore>0</pol:creditScore> <pol:price>0</pol:price> </pol:policyQuoteInfo> </pol:receivePolicyQuote> </pol:policyQuote> </soapenv:Body> </soapenv:Envelope> to this URL http://localhost:8080/PolicyQuoteProcessServiceService/PolicyQuoteProcess... 2) Then wait until you see the following on the console: Received Driving Record Request for: Bill Smith 3) Then send: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:drv="http://dmv.com/drivingRecord"> <soapenv:Header/> <soapenv:Body> <drv:drivingRecordResponse> <drv:name>Bill Smith</drv:name> <drv:ssn>412345678</drv:ssn> <drv:dlNumber>987654321</drv:dlNumber> <drv:age>30</drv:age> <drv:numberOfTickets>2</drv:numberOfTickets> <drv:numberOfAccidents>1</drv:numberOfAccidents> </drv:drivingRecordResponse> </soapenv:Body> </soapenv:Envelope> to http://localhost:8080/PolicyQuoteProcessServiceService/DrivingRecordCallb... (The example has been provided by Jeff DeLong). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-2157) Child nodes truncated when using jaxb to marshall data into a SOAP header

by Andrew Dinn (JIRA)

Child nodes truncated when using jaxb to marshall data into a SOAP header -------------------------------------------------------------------------- Key: JBWS-2157 URL: http://jira.jboss.com/jira/browse/JBWS-2157 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Andrew Dinn I wish to serialise a CoordinationContext type (a complex type defined in the OASIS WS-COOR 1.1 spec) into a SOAP message header as follows: <code> final JAXBContext jaxbCtx = getJaxbContext(); final SOAPMessage soapMessage = context.getMessage(); final SOAPEnvelope soapEnvelope = soapMessage.getSOAPPart().getEnvelope(); SOAPHeader soapHeader = soapEnvelope.getHeader() ; if (soapHeader == null) { soapHeader = soapEnvelope.addHeader() ; } Marshaller marshaller = jaxbCtx.createMarshaller(); marshaller.marshal(coordinationContext, soapHeader); </code> The problem is that the header gets inserted without any children. What happens is that the marshaller creates a SOAP tree top down consisting of SOAPElementImpl instances. It inserts these nodes into the tree below the SOAPHeader as it creates them. So, when the first node is created a call to SOAPHeader.addchild() is made. This call deteccts that the supplied node is of the wrong type so it substitutes a SOAPHeaderElementImpl. It attempts to copy the supplied node's substructure but the marshaller has not created the children at this point. -- 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, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-3252) Investigate WSA interop tests regression

by Richard Opalka (JIRA)

Investigate WSA interop tests regression ---------------------------------------- Key: JBWS-3252 URL: https://issues.jboss.org/browse/JBWS-3252 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 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 April 2011