May 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3797) Let @WebContext(virtualHost...) affect endpoint address

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3797: ------------------------------------- Summary: Let @WebContext(virtualHost...) affect endpoint address Key: JBWS-3797 URL: https://issues.jboss.org/browse/JBWS-3797 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-5.0 When @WerbContext(virtualHost=...) is specified, the referenced virtualHost name should be usable to get the corresponding port (from the web layer, through the (JBoss)WebMetadata attached to deployment) and modify the endpoint address accordingly (in EndpointAddressDeploymentAspect). This likely require some additional functionalities from the container web layer to get the port for a given virtual host. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3773: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1077262|https://bugzilla.redhat.com/show_bug.cgi?id=1077262] from NEW to POST > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3796) CXFHandlerResolverImpl initializes handlers at each getHandlerChain() invocation

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3796: ------------------------------------- Summary: CXFHandlerResolverImpl initializes handlers at each getHandlerChain() invocation Key: JBWS-3796 URL: https://issues.jboss.org/browse/JBWS-3796 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 org.jboss.wsf.stack.cxf.client.serviceref.CXFHandlerResolverImpl#getHandlerChain(PortInfo portInfo) uses a map to avoid building the handler chain multiple time for a given port info. However it performs initialization / injection on the handlers at each invocation. Moreover, the access to the map is not thread-safe. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3773: ----------------------------------------------- Jan Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1077259|https://bugzilla.redhat.com/show_bug.cgi?id=1077259] from ON_QA to VERIFIED > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3795) Improve and fix org.jboss.ws.api.handler.* classes

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3795: ------------------------------------- Summary: Improve and fix org.jboss.ws.api.handler.* classes Key: JBWS-3795 URL: https://issues.jboss.org/browse/JBWS-3795 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 The convenient handler utility classes in org.jboss.ws.api.handler package needs to be fixed to remove some warnings related to generics, make GenericSOAPHandler declare SOAPMessageContext parameter (instead of wrong LogicalMessageContext) and possibly make them thread-safe. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3682) Anonymous types in an exception aren't generated in WSDL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3682?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3682: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > Anonymous types in an exception aren't generated in WSDL > -------------------------------------------------------- > > Key: JBWS-3682 > URL: https://issues.jboss.org/browse/JBWS-3682 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2 > Reporter: Tadayoshi Sato > Fix For: jbossws-cxf-5.0 > > Attachments: exception-anontype.zip > > > This is a CXF issue: https://issues.apache.org/jira/browse/CXF-5208 > Anonymous types (annotated with {{@XmlType(name = "")}}) in an exception class aren't generated at all in WSDL. > Web service classes: > {code:java} > @WebService > public class GreetingService { > @WebMethod > public void hello() throws MyException {} > ... > {code} > {code:java} > public class MyException extends Exception { > private String str; > private MyAnonType myAnonObj; > public String getStr() { return str; } > public void setStr(String str) { this.str = str; } > public MyAnonType getMyAnonObj() { return myAnonObj; } > public void setMyAnonObj(MyAnonType myAnonObj) { this.myAnonObj = myAnonObj; } > ... > {code} > {code:java} > @XmlType(name = "") > public class MyAnonType { ... > {code} > Generated WSDL: > {code:xml} > <wsdl:types> > <xs:schema ...> > ... > <xs:complexType name="MyException"> > <xs:sequence> > <xs:element name="str" nillable="true" type="xs:string"/> > </xs:sequence> > </xs:complexType> > {code} > Note that the same type ({{MyAnonType}}) is generated in WSDL if the {{@XmlType(name = "")}} annotation is removed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3794) Create WildFly 8.1 ASIL

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3794: ------------------------------------- Summary: Create WildFly 8.1 ASIL Key: JBWS-3794 URL: https://issues.jboss.org/browse/JBWS-3794 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-5.0 As soon as WildFly 8.1.0 goes Final, we need to create proper AS integration layer branch. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3750) Add ability to rewrite path in WSDL URL references

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3750: -------------------------------- I don't think this enhancement is going to function the way you intend. The format for a URL/URI is [scheme:][//[host]:[port]][path][?query][#fragment] If I have the following services declared in a wsdl http://localhost:8080/jaxws-jbws2150/ValidURL http://localhost:8080/jaxws-jbws2150/InvalidURL then there are 2 unique paths, "jaxws-jbws2150/ValidURL" and "jaxws-jbws2150/InvalidURL". This enhancement replaces each path with a single custom path. If I set the custom path to "/my-custom-path/foo/bar" the 2 addresses above become http://localhost:8080/my-custom-path/foo/bar http://localhost:8080/my-custom-path/foo/bar Is this what is intended? > Add ability to rewrite path in WSDL URL references > -------------------------------------------------- > > Key: JBWS-3750 > URL: https://issues.jboss.org/browse/JBWS-3750 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Kyle Lape > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > > Currently JBossWS/CXF have the ability to configure a custom host and/or port to use when populating the soap:address and schemaLocation items in a WSDL. This request is to add the ability to configure a custom URL path in addition to the host and port. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3773: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1077259|https://bugzilla.redhat.com/show_bug.cgi?id=1077259] from MODIFIED to ON_QA > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3792) JBossWS: wsdl:import always handled as relative location

by Marc H. (JIRA)

[ https://issues.jboss.org/browse/JBWS-3792?page=com.atlassian.jira.plugin.... ] Marc H. updated JBWS-3792: -------------------------- Attachment: JBWS-3792_java.net.URL_proposal.patch Note that the problem also affect locations containing only an absolute path (starting with a slash): "http://test.com/1/2" and "/a/b" will be resolved to "http://test.com/1/2/a/b" instead of "http://test.com/a/b". A straightforward fix could be to resolve the context using directly the java.net.URL API which already implements RFC-2396 specificities (see patch attached)... Is there any chance to see this jbossws-cxf-4.3.1 ? (I guess that jbossws-cxf-5, will not be available before a while). > JBossWS: wsdl:import always handled as relative location > -------------------------------------------------------- > > Key: JBWS-3792 > URL: https://issues.jboss.org/browse/JBWS-3792 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Marc H. > Fix For: jbossws-cxf-5.0 > > Attachments: JBWS-3792_java.net.URL_proposal.patch > > > As described in this thread: https://community.jboss.org/thread/240821 > wsdl:import directive seems to be always resolved as a relative location. > For example, this statement: > <wsdl:import namespace="http://foo.bar.com/foo.bar.Service" location="http://foo.bar.com/Service.svc?wsdl=wsdl0"/> > May result in this URL being resolved: > http://foo.bar.com/http://foo.bar.com/Service.svc?wsdl=wsdl0 > This prevents the WSDL file from being parsed. > This behavior seems to originate from: org.jboss.ws.common.deployment.SOAPAddressWSDLParser, line 211 in v2.3.0.Final and current trunk: > } else if (match(reader, WSDL_NS, IMPORT)) { > final String location = reader.getAttributeValue(null, LOCATION); > final String url = wsdlUrl.toString(); > final String newUrl = url.substring(0, url.lastIndexOf("/") + (location.startsWith("/") ? 0 : 1)) + location; > if (!metadata.getImports().containsKey(newUrl)) { > metadata.getImports().put(newUrl, false); > } > } -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 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 May 2014