September 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3354) CXF does not set the correct host when viewing WSDLs that are published with JAXWS API

by Magesh Bojan (JIRA)

CXF does not set the correct host when viewing WSDLs that are published with JAXWS API -------------------------------------------------------------------------------------- Key: JBWS-3354 URL: https://issues.jboss.org/browse/JBWS-3354 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.0.0.Beta3 Reporter: Magesh Bojan https://issues.apache.org/jira/browse/CXF-3787 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3353) JBossWSTestHelper's getIntegrationTarget() method needs upgrade

by Boris Belovic (JIRA)

JBossWSTestHelper's getIntegrationTarget() method needs upgrade --------------------------------------------------------------- Key: JBWS-3353 URL: https://issues.jboss.org/browse/JBWS-3353 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: RHEL_{4,5}, JDK 1.6 Reporter: Boris Belovic JBossWSTestHelper's getIntegrationTarget() method checks for these versions of AS/EAP 5.0, 5.1, 6.0 and 6.1. For other values it throws IllegalStateException. This causes problems when running testsuite against products with different version number e.g. SOA-Platform 5.2. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3351) Change AS6 Integraiton layer to build and deploy EJB3 endpoint in a war file

by Jim Ma (JIRA)

Change AS6 Integraiton layer to build and deploy EJB3 endpoint in a war file ----------------------------------------------------------------------------- Key: JBWS-3351 URL: https://issues.jboss.org/browse/JBWS-3351 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3350) Change AS7 Integraiton layer to build and deploy EJB3 endpoint in a war file

by Jim Ma (JIRA)

Change AS7 Integraiton layer to build and deploy EJB3 endpoint in a war file ----------------------------------------------------------------------------- Key: JBWS-3350 URL: https://issues.jboss.org/browse/JBWS-3350 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3348) Get rid of org.jboss.ws.backward_compatible_context_creator property

by Richard Opalka (JIRA)

Get rid of org.jboss.ws.backward_compatible_context_creator property -------------------------------------------------------------------- Key: JBWS-3348 URL: https://issues.jboss.org/browse/JBWS-3348 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 There's no more need to keep this BC property. AS6 was based on this and users had enough time to switch from JBossAS 5x series to JBossAS 6x. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3347) Endpoints created through Endpoint.publish throws Address already in use: bind

by Magesh Bojan (JIRA)

Endpoints created through Endpoint.publish throws Address already in use: bind ------------------------------------------------------------------------------ Key: JBWS-3347 URL: https://issues.jboss.org/browse/JBWS-3347 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-cxf-4.0.0.Beta3 Environment: AS7 Reporter: Magesh Bojan At AS7 server startup, all deployments are deployed in a batch and multiple threads can call createHttpServerEngine. Although the method is synchronized, the behavior is not as expected. The Engine gets created multiple times for the same port and results in Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use: bind at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerEngine.addHandler(HttpServerEngine.java:103) at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerDestination.activate(HttpServerDestination.java:128) at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48) at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:97) at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:836) at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127) at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:341) ... 15 more Caused by: java.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind(Native Method) [:1.6.0_26] at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) [:1.6.0_26] at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) [:1.6.0_26] at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:112) at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:47) at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:37) at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:126) at org.jboss.wsf.stack.cxf.addons.transports.httpserver.HttpServerEngine.addHandler(HttpServerEngine.java:94) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

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

by Kyle Lape (JIRA)

Preamble is omitted when supplying WSDL and external XSDs --------------------------------------------------------- Key: JBWS-3345 URL: https://issues.jboss.org/browse/JBWS-3345 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 Assignee: 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: {noformat}http://localhost:8080/testService/Service?wsdl&resource=external.xsd{noformat} The file on the server starts like this: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <xsd:schema ...> ... </xsd:schema> {code} But when it's served to a client, it starts like this: {code:xml} <xsd:schema ...> ... </xsd:schema> {code} This affects the WSDL and any resources referenced by the WSDL. Looking at the code, this is what happens when a request for a WSDL resource is received: - The WSDL resource is read in from the file system. - It is then parsed into a DOM tree. - JBossWS then replaces references to external resources with appropriate URLs that can be reached using "?wsdl" URLs. - The DOM tree is then marshaled to XML text. In this process, the XML preamble is lost. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues September 2011