Issues with Attachments: week of 2015-04-13

2015-04-13 Thread dkulp
 
CXF - Monday, April 13, 2015
 
  3 Issues with Attachments
 
  (sorted oldest to newest)
 
[CXF-6274] NullPointerException in DestinationSequence because of 
RMCaptureInInterceptor not in interceptor chain
  - Created: 2015-03-05
  - Updated: 2015-03-30
  - Type: Bug
  - Fix Versions: [3.0.5]
  - Reporter: Jochen Riedlinger
  - Assigned: Akitoshi Yoshida
  - Attachments: [cxf-servlet.xml, ws-rm_saml.wsdl]
  - https://issues.apache.org/jira/browse/CXF-6274
 
[CXF-6315] Optional WS-Addressing policy doesn't return required soap 
headers
  - Created: 2015-03-23
  - Updated: 2015-03-23
  - Type: Bug
  - Fix Versions: []
  - Reporter: Oliver Wulff
  - Assigned: Unassigned
  - Attachments: [test_rm.tar.gz]
  - https://issues.apache.org/jira/browse/CXF-6315
 
[CXF-6330] HTTPConduit does not enforce configuration constraints
  - Created: 2015-04-04
  - Updated: 2015-04-04
  - Type: Bug
  - Fix Versions: []
  - Reporter: John McNair
  - Assigned: Unassigned
  - Attachments: [cxf-http-client-policy-bug.tar.gz]
  - https://issues.apache.org/jira/browse/CXF-6330
 


[jira] [Created] (CXF-6347) CXF bundle activators not called in Eclipse/Equinox

2015-04-13 Thread Thorsten Meinl (JIRA)
Thorsten Meinl created CXF-6347:
---

 Summary: CXF bundle activators not called in Eclipse/Equinox
 Key: CXF-6347
 URL: https://issues.apache.org/jira/browse/CXF-6347
 Project: CXF
  Issue Type: Bug
  Components: OSGi
Affects Versions: 3.0.4
 Environment: Eclipse 4.4
Reporter: Thorsten Meinl


The CXF bundles have OSGi activators that perform initialization stuff such as 
looking for CXF services in other bundles. However, in Equinox the bundle 
activators are not called unless one explicitly starts the bundles. The default 
strategy in Equinox is not to start bundles, unless the 
"Bundle-ActivationPolicy" is set to "lazy". Therefore this header should be 
added to all bundles so that CXF (esp. the client) is also usable inside an 
Eclipse application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CXF-4109) UriInfo getHost caches first request's host and always returns that on subsequent calls

2015-04-13 Thread Knut-Olav Hoven (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492140#comment-14492140
 ] 

Knut-Olav Hoven commented on CXF-4109:
--

I tried to look at the code in Fisheye, but I just can't make sense of the 
presentation of the commit on the link you posted...
Looks to me that the commit has no changes... or might be just me not 
understanding hos Fisheye works... ;)

We worked around the issue by supplying a init-param 
*disable-address-updates=true* in web.xml:
{code}

CXFServlet

org.apache.cxf.transport.servlet.CXFServlet

disable-address-updates
true

1

{code}

> UriInfo getHost caches first request's host and always returns that on 
> subsequent calls
> ---
>
> Key: CXF-4109
> URL: https://issues.apache.org/jira/browse/CXF-4109
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 2.5.2
> Environment: Linux CentOS 6
>Reporter: Dan Hintz
>Assignee: Sergey Beryozkin
> Fix For: 2.4.7, 2.5.3, 2.6
>
>
> The call to UriInfo.getHost() is caching the first request's host and always 
> returning that on all subsequent calls.
> For example, Tomcat starts up and a request is made to the server using a URL 
> of "http://1.2.3.4/apicall";, getHost() returns "1.2.3.4", the next request is 
> made using a URL of "http://mydomainname.com/apicall";, getHost() still 
> returns "1.2.3.4", where "mydomainname.com" is expected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (CXF-4109) UriInfo getHost caches first request's host and always returns that on subsequent calls

2015-04-13 Thread Knut-Olav Hoven (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492140#comment-14492140
 ] 

Knut-Olav Hoven edited comment on CXF-4109 at 4/13/15 9:51 AM:
---

I tried to look at the code in Fisheye, but I just can't make sense of the 
presentation of the commit on the link you posted...
Looks to me that the commit has no changes... or might be just me not 
understanding hos Fisheye works... ;)

We worked around the issue by supplying a init-param 
*disable-address-updates=true* in web.xml:
{code}

CXFServlet

org.apache.cxf.transport.servlet.CXFServlet

disable-address-updates
true

1

{code}


As a side note... this init-param seems to have a logical flaw... since I in 
any other situation would read the name of the init-param as functioning the 
other way around, that updating of the address would now be disabled (aka 
cached), instead of forcing it to be updated.


was (Author: hovenko):
I tried to look at the code in Fisheye, but I just can't make sense of the 
presentation of the commit on the link you posted...
Looks to me that the commit has no changes... or might be just me not 
understanding hos Fisheye works... ;)

We worked around the issue by supplying a init-param 
*disable-address-updates=true* in web.xml:
{code}

CXFServlet

org.apache.cxf.transport.servlet.CXFServlet

disable-address-updates
true

1

{code}

> UriInfo getHost caches first request's host and always returns that on 
> subsequent calls
> ---
>
> Key: CXF-4109
> URL: https://issues.apache.org/jira/browse/CXF-4109
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 2.5.2
> Environment: Linux CentOS 6
>Reporter: Dan Hintz
>Assignee: Sergey Beryozkin
> Fix For: 2.4.7, 2.5.3, 2.6
>
>
> The call to UriInfo.getHost() is caching the first request's host and always 
> returning that on all subsequent calls.
> For example, Tomcat starts up and a request is made to the server using a URL 
> of "http://1.2.3.4/apicall";, getHost() returns "1.2.3.4", the next request is 
> made using a URL of "http://mydomainname.com/apicall";, getHost() still 
> returns "1.2.3.4", where "mydomainname.com" is expected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread carvin (JIRA)
carvin created CXF-6348:
---

 Summary: POST data missing in HttpServletRequest
 Key: CXF-6348
 URL: https://issues.apache.org/jira/browse/CXF-6348
 Project: CXF
  Issue Type: Bug
  Components: JAX-RS
 Environment: Tomcat maven plugin 2.2
JDK 1.7.0_60
Reporter: carvin


Code:
== Service ==
{code}
@Path("/login")
public class LoginService {
@POST
@Produces(MediaType.TEXT_PLAIN)
@Consumes(MediaType.APPLICATION_FORM_URLENCODED)
public String login(@Context HttpServletRequest request) {
String name = request.getParameter("name");

System.out.println("name : " + name); // The name is null
if("test".equals(name)) {
return "SUCCESS";
}
return "FAIL";
}
}
{code}
== Spring config file ==
{code:xml}

http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xmlns:jaxrs="http://cxf.apache.org/jaxrs";
   xsi:schemaLocation="http://www.springframework.org/schema/beans
   http://www.springframework.org/schema/beans/spring-beans.xsd
   http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>

















{code}

=== web.xml ===
{code:xml}

http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
version="3.0"
metadata-complete="false">


contextConfigLocation

classpath*:spring/spring-*.xml





org.springframework.web.context.ContextLoaderListener



CXFServlet

org.apache.cxf.transport.servlet.CXFServlet


CXFServlet
/services/*


{code}

=== Test html file ===
{code:xml}






http://localhost:8080/cxf/services/login";>
name:

submit



function visit() {
document.getElementById("fm").submit();
}



{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread carvin (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

carvin updated CXF-6348:

Affects Version/s: 3.0.4

> POST data missing in HttpServletRequest
> ---
>
> Key: CXF-6348
> URL: https://issues.apache.org/jira/browse/CXF-6348
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.0.4
> Environment: Tomcat maven plugin 2.2
> JDK 1.7.0_60
>Reporter: carvin
>
> Code:
> == Service ==
> {code}
> @Path("/login")
> public class LoginService {
> @POST
> @Produces(MediaType.TEXT_PLAIN)
> @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
> public String login(@Context HttpServletRequest request) {
> String name = request.getParameter("name");
> System.out.println("name : " + name); // The name is null
> if("test".equals(name)) {
> return "SUCCESS";
> }
> return "FAIL";
> }
> }
> {code}
> == Spring config file ==
> {code:xml}
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> === web.xml ===
> {code:xml}
> 
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
> version="3.0"
> metadata-complete="false">
> 
> contextConfigLocation
> 
> classpath*:spring/spring-*.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
> 
> CXFServlet
> 
> org.apache.cxf.transport.servlet.CXFServlet
> 
> 
> CXFServlet
> /services/*
> 
> 
> {code}
> === Test html file ===
> {code:xml}
> 
> 
> 
>   
> 
> 
> http://localhost:8080/cxf/services/login";>
>   name:
> 
> submit
> 
> function visit() {
>   document.getElementById("fm").submit();
> }
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread carvin (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

carvin updated CXF-6348:

Environment: 
Tomcat maven plugin 2.2
JDK 1.7.0_60
CXF 3.0.4 
Spring 3.2.13.RELEASE

  was:
Tomcat maven plugin 2.2
JDK 1.7.0_60


> POST data missing in HttpServletRequest
> ---
>
> Key: CXF-6348
> URL: https://issues.apache.org/jira/browse/CXF-6348
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.0.4
> Environment: Tomcat maven plugin 2.2
> JDK 1.7.0_60
> CXF 3.0.4 
> Spring 3.2.13.RELEASE
>Reporter: carvin
>
> Code:
> == Service ==
> {code}
> @Path("/login")
> public class LoginService {
> @POST
> @Produces(MediaType.TEXT_PLAIN)
> @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
> public String login(@Context HttpServletRequest request) {
> String name = request.getParameter("name");
> System.out.println("name : " + name); // The name is null
> if("test".equals(name)) {
> return "SUCCESS";
> }
> return "FAIL";
> }
> }
> {code}
> == Spring config file ==
> {code:xml}
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> === web.xml ===
> {code:xml}
> 
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
> version="3.0"
> metadata-complete="false">
> 
> contextConfigLocation
> 
> classpath*:spring/spring-*.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
> 
> CXFServlet
> 
> org.apache.cxf.transport.servlet.CXFServlet
> 
> 
> CXFServlet
> /services/*
> 
> 
> {code}
> === Test html file ===
> {code:xml}
> 
> 
> 
>   
> 
> 
> http://localhost:8080/cxf/services/login";>
>   name:
> 
> submit
> 
> function visit() {
>   document.getElementById("fm").submit();
> }
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread carvin (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

carvin updated CXF-6348:

Environment: 
Tomcat maven plugin 2.2 OR Jetty maven plugin 9.2.10.v20150310
JDK 1.7.0_60
CXF 3.0.4 
Spring 3.2.13.RELEASE

  was:
Tomcat maven plugin 2.2
JDK 1.7.0_60
CXF 3.0.4 
Spring 3.2.13.RELEASE


> POST data missing in HttpServletRequest
> ---
>
> Key: CXF-6348
> URL: https://issues.apache.org/jira/browse/CXF-6348
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.0.4
> Environment: Tomcat maven plugin 2.2 OR Jetty maven plugin 
> 9.2.10.v20150310
> JDK 1.7.0_60
> CXF 3.0.4 
> Spring 3.2.13.RELEASE
>Reporter: carvin
>
> Code:
> == Service ==
> {code}
> @Path("/login")
> public class LoginService {
> @POST
> @Produces(MediaType.TEXT_PLAIN)
> @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
> public String login(@Context HttpServletRequest request) {
> String name = request.getParameter("name");
> System.out.println("name : " + name); // The name is null
> if("test".equals(name)) {
> return "SUCCESS";
> }
> return "FAIL";
> }
> }
> {code}
> == Spring config file ==
> {code:xml}
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> === web.xml ===
> {code:xml}
> 
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
> version="3.0"
> metadata-complete="false">
> 
> contextConfigLocation
> 
> classpath*:spring/spring-*.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
> 
> CXFServlet
> 
> org.apache.cxf.transport.servlet.CXFServlet
> 
> 
> CXFServlet
> /services/*
> 
> 
> {code}
> === Test html file ===
> {code:xml}
> 
> 
> 
>   
> 
> 
> http://localhost:8080/cxf/services/login";>
>   name:
> 
> submit
> 
> function visit() {
>   document.getElementById("fm").submit();
> }
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CXF-6335) Explicitly set HTTPConduit on client inbound message

2015-04-13 Thread Alessio Soldano (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alessio Soldano resolved CXF-6335.
--
Resolution: Fixed

> Explicitly set HTTPConduit on client inbound message
> 
>
> Key: CXF-6335
> URL: https://issues.apache.org/jira/browse/CXF-6335
> Project: CXF
>  Issue Type: Improvement
>  Components: JAX-WS Runtime, Transports
>Reporter: Alessio Soldano
>Assignee: Alessio Soldano
> Fix For: 3.1.0, 3.0.5
>
>
> On client side, an instance of HTTPConduit is saved in the Message when the 
> ConduitSelector is used on client (in particular, the prepare(Message 
> message) method is called on the selector). That applies to the oubound 
> message only, though. The inbound message is not explicitly linked to the 
> conduit, untill something actually needs it (lazy approach), for instance the 
> PolicyInVerificationInterceptor.
> This is a problem as the selector clears the message context cache after 
> having selected the conduit, which is a performance issue as we end up 
> computing the cache twice for response messages. The conduit should be 
> selected (actually copied from the outbound message) soon after having 
> created the response inbound Message, to prevent double cache computing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FEDIZ-65) REST interface for IDP

2015-04-13 Thread Colm O hEigeartaigh (JIRA)

[ 
https://issues.apache.org/jira/browse/FEDIZ-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492526#comment-14492526
 ] 

Colm O hEigeartaigh commented on FEDIZ-65:
--

Can this issue be resolved or is there any more work to be done?

Colm.

> REST interface for IDP
> --
>
> Key: FEDIZ-65
> URL: https://issues.apache.org/jira/browse/FEDIZ-65
> Project: CXF-Fediz
>  Issue Type: New Feature
>  Components: IDP
>Affects Versions: 1.1.0
>Reporter: Oliver Wulff
> Fix For: 1.2.0
>
>
> Provide REST interfaces:
> - to get current status of a user session (debug purpose)
> - read IDP configurations (trusted IDP, service configs, etc.)
> - update IDP configurations



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CXF-4109) UriInfo getHost caches first request's host and always returns that on subsequent calls

2015-04-13 Thread Sergey Beryozkin (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492585#comment-14492585
 ] 

Sergey Beryozkin commented on CXF-4109:
---

Ok, thanks for the confirmation. I did not notice it was CXF 2.5.2.
This is a known workaround, and it this property is enabled by default in CXF 
3.0.x


> UriInfo getHost caches first request's host and always returns that on 
> subsequent calls
> ---
>
> Key: CXF-4109
> URL: https://issues.apache.org/jira/browse/CXF-4109
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 2.5.2
> Environment: Linux CentOS 6
>Reporter: Dan Hintz
>Assignee: Sergey Beryozkin
> Fix For: 2.4.7, 2.5.3, 2.6
>
>
> The call to UriInfo.getHost() is caching the first request's host and always 
> returning that on all subsequent calls.
> For example, Tomcat starts up and a request is made to the server using a URL 
> of "http://1.2.3.4/apicall";, getHost() returns "1.2.3.4", the next request is 
> made using a URL of "http://mydomainname.com/apicall";, getHost() still 
> returns "1.2.3.4", where "mydomainname.com" is expected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CXF-6339) CXF Client platform dependent problem: javax.xml.ws.soap.SOAPFaultException: No conduit initiator was found for the namespace http://schemas.xmlsoap.org/soap/http.

2015-04-13 Thread Daniel Kulp (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-6339.
--
   Resolution: Invalid
Fix Version/s: Invalid

This is really an issue/question for the users list.   THere is a miss-match of 
cxf versions which need to be resolved.

> CXF Client platform dependent problem: javax.xml.ws.soap.SOAPFaultException: 
> No conduit initiator was found for the namespace 
> http://schemas.xmlsoap.org/soap/http.
> ---
>
> Key: CXF-6339
> URL: https://issues.apache.org/jira/browse/CXF-6339
> Project: CXF
>  Issue Type: Bug
>  Components: Soap Binding
>Affects Versions: 2.5
> Environment: Stack: cedar-10
> Framework: Play 2.x - Java
> JavaOpts:  -Xss512k -XX:+UseCompressedOops
> SBT_OPTS : -Xss512k -XX:+UseCompressedOops
> OpenJDK 1.8, 64-Bit Server VM
> deployed on herokuapp.com, cannot determine platform on which I have problem 
> - some deploys don't throw exceptions, some throw
>Reporter: Sergio Shapoval
>Priority: Blocker
> Fix For: Invalid
>
>
> Hi, 
> I am using herokuapp.com for staging my app.
> Several builds are throwing next error when I am trying to make any SOAP 
> request:
> https://www.dropbox.com/s/pj1aqkcwkc0to71/errorLog.txt?dl=0
> I have generated CXF client by wsdl2java:
> https://www.dropbox.com/s/nao5ilph11k8f3j/pom.xml?dl=0
> I am using generated classes in next configuration of play framework - 
> https://www.dropbox.com/s/iy88w0g5opqf1zt/build.sbt?dl=0
> I have tryed to add additional dependencies or cancel requests validation as 
> it was described here - 
> http://stackoverflow.com/questions/7611803/cxf-2-4-2-no-conduit-initiator-was-found-for-the-namespace-http-schemas-xmlso
>   JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
>   factory.getInInterceptors().add(new LoggingInInterceptor());
>   factory.getOutInterceptors().add(new LoggingOutInterceptor());
>   Logger.info("webServiceAddress:" + webServiceAddress);
>   factory.setAddress(webServiceAddress);
>   factory.setServiceClass(clazz);
>   factory.setProperties(new HashMap(){{
>   put("schema-validation-enabled", false);
>   put("set-jaxb-validation-event-handler", false);
>   }});
>   Logger.info("service factory:" + factory);
>   return factory.create();
> but no success.
> when I make SOAP requests on localhost or test my app in https://codeship.com 
> I don't have such problem.
> so, I think it is platform dependent problem.
> How I can resolve this error?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (CXF-6339) CXF Client platform dependent problem: javax.xml.ws.soap.SOAPFaultException: No conduit initiator was found for the namespace http://schemas.xmlsoap.org/soap/http.

2015-04-13 Thread Sergio Shapoval (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergio Shapoval closed CXF-6339.


matched all versions to 2.5.6, others deleted

> CXF Client platform dependent problem: javax.xml.ws.soap.SOAPFaultException: 
> No conduit initiator was found for the namespace 
> http://schemas.xmlsoap.org/soap/http.
> ---
>
> Key: CXF-6339
> URL: https://issues.apache.org/jira/browse/CXF-6339
> Project: CXF
>  Issue Type: Bug
>  Components: Soap Binding
>Affects Versions: 2.5
> Environment: Stack: cedar-10
> Framework: Play 2.x - Java
> JavaOpts:  -Xss512k -XX:+UseCompressedOops
> SBT_OPTS : -Xss512k -XX:+UseCompressedOops
> OpenJDK 1.8, 64-Bit Server VM
> deployed on herokuapp.com, cannot determine platform on which I have problem 
> - some deploys don't throw exceptions, some throw
>Reporter: Sergio Shapoval
>Priority: Blocker
> Fix For: Invalid
>
>
> Hi, 
> I am using herokuapp.com for staging my app.
> Several builds are throwing next error when I am trying to make any SOAP 
> request:
> https://www.dropbox.com/s/pj1aqkcwkc0to71/errorLog.txt?dl=0
> I have generated CXF client by wsdl2java:
> https://www.dropbox.com/s/nao5ilph11k8f3j/pom.xml?dl=0
> I am using generated classes in next configuration of play framework - 
> https://www.dropbox.com/s/iy88w0g5opqf1zt/build.sbt?dl=0
> I have tryed to add additional dependencies or cancel requests validation as 
> it was described here - 
> http://stackoverflow.com/questions/7611803/cxf-2-4-2-no-conduit-initiator-was-found-for-the-namespace-http-schemas-xmlso
>   JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
>   factory.getInInterceptors().add(new LoggingInInterceptor());
>   factory.getOutInterceptors().add(new LoggingOutInterceptor());
>   Logger.info("webServiceAddress:" + webServiceAddress);
>   factory.setAddress(webServiceAddress);
>   factory.setServiceClass(clazz);
>   factory.setProperties(new HashMap(){{
>   put("schema-validation-enabled", false);
>   put("set-jaxb-validation-event-handler", false);
>   }});
>   Logger.info("service factory:" + factory);
>   return factory.create();
> but no success.
> when I make SOAP requests on localhost or test my app in https://codeship.com 
> I don't have such problem.
> so, I think it is platform dependent problem.
> How I can resolve this error?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CXF-6349) Introduce HTTP/2 Transport

2015-04-13 Thread Sergey Beryozkin (JIRA)
Sergey Beryozkin created CXF-6349:
-

 Summary: Introduce HTTP/2 Transport 
 Key: CXF-6349
 URL: https://issues.apache.org/jira/browse/CXF-6349
 Project: CXF
  Issue Type: New Feature
  Components: Transports
Reporter: Sergey Beryozkin
 Fix For: NeedMoreInfo


https://http2.github.io/

Can be complimentary to what Aki has done with WebSockets. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CXF-6349) Introduce HTTP/2 Transport

2015-04-13 Thread Sergey Beryozkin (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Beryozkin updated CXF-6349:
--
Description: 
https://http2.github.io/

Can be complementary to what Aki has done with WebSockets. 

  was:
https://http2.github.io/

Can be complimentary to what Aki has done with WebSockets. 


> Introduce HTTP/2 Transport 
> ---
>
> Key: CXF-6349
> URL: https://issues.apache.org/jira/browse/CXF-6349
> Project: CXF
>  Issue Type: New Feature
>  Components: Transports
>Reporter: Sergey Beryozkin
> Fix For: NeedMoreInfo
>
>
> https://http2.github.io/
> Can be complementary to what Aki has done with WebSockets. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CXF-6349) Introduce HTTP/2 Transport

2015-04-13 Thread Sergey Beryozkin (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492936#comment-14492936
 ] 

Sergey Beryozkin commented on CXF-6349:
---

Apparently Jetty implements it

> Introduce HTTP/2 Transport 
> ---
>
> Key: CXF-6349
> URL: https://issues.apache.org/jira/browse/CXF-6349
> Project: CXF
>  Issue Type: New Feature
>  Components: Transports
>Reporter: Sergey Beryozkin
> Fix For: NeedMoreInfo
>
>
> https://http2.github.io/
> Can be complementary to what Aki has done with WebSockets. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CXF-6315) Optional WS-Addressing policy doesn't return required soap headers

2015-04-13 Thread Daniel Kulp (JIRA)

 [ 
https://issues.apache.org/jira/browse/CXF-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-6315.
--
   Resolution: Fixed
Fix Version/s: 3.0.5
 Assignee: Daniel Kulp

> Optional WS-Addressing policy doesn't return required soap headers
> --
>
> Key: CXF-6315
> URL: https://issues.apache.org/jira/browse/CXF-6315
> Project: CXF
>  Issue Type: Bug
>  Components: WS-* Components
>Affects Versions: 2.7.15
>Reporter: Oliver Wulff
>Assignee: Daniel Kulp
> Fix For: 3.0.5
>
> Attachments: test_rm.tar.gz
>
>
> If the service provider defines an optional WS-Addressing policy and the 
> service consumer sends WS-Addressing headers, the server doesn't add the 
> required WS-Addressing headers in the response.
> Might be related to CXF-5645



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread Sergey Beryozkin (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493029#comment-14493029
 ] 

Sergey Beryozkin commented on CXF-6348:
---

Well, I'm not sure a JAX-RS runtime is responsible for populating 
HttpServletRequest with name/values extracted from a form payload, it has to be 
able to read them into a JAX-RS Form or MultipartMap.

> POST data missing in HttpServletRequest
> ---
>
> Key: CXF-6348
> URL: https://issues.apache.org/jira/browse/CXF-6348
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.0.4
> Environment: Tomcat maven plugin 2.2 OR Jetty maven plugin 
> 9.2.10.v20150310
> JDK 1.7.0_60
> CXF 3.0.4 
> Spring 3.2.13.RELEASE
>Reporter: carvin
>
> Code:
> == Service ==
> {code}
> @Path("/login")
> public class LoginService {
> @POST
> @Produces(MediaType.TEXT_PLAIN)
> @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
> public String login(@Context HttpServletRequest request) {
> String name = request.getParameter("name");
> System.out.println("name : " + name); // The name is null
> if("test".equals(name)) {
> return "SUCCESS";
> }
> return "FAIL";
> }
> }
> {code}
> == Spring config file ==
> {code:xml}
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> === web.xml ===
> {code:xml}
> 
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
> version="3.0"
> metadata-complete="false">
> 
> contextConfigLocation
> 
> classpath*:spring/spring-*.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
> 
> CXFServlet
> 
> org.apache.cxf.transport.servlet.CXFServlet
> 
> 
> CXFServlet
> /services/*
> 
> 
> {code}
> === Test html file ===
> {code:xml}
> 
> 
> 
>   
> 
> 
> http://localhost:8080/cxf/services/login";>
>   name:
> 
> submit
> 
> function visit() {
>   document.getElementById("fm").submit();
> }
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread carvin (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493444#comment-14493444
 ] 

carvin commented on CXF-6348:
-

Thanks a lot for your reply, and I think the users were more accustomed to use 
the HttpServletRequest  to get the parameters. 


> POST data missing in HttpServletRequest
> ---
>
> Key: CXF-6348
> URL: https://issues.apache.org/jira/browse/CXF-6348
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.0.4
> Environment: Tomcat maven plugin 2.2 OR Jetty maven plugin 
> 9.2.10.v20150310
> JDK 1.7.0_60
> CXF 3.0.4 
> Spring 3.2.13.RELEASE
>Reporter: carvin
>
> Code:
> == Service ==
> {code}
> @Path("/login")
> public class LoginService {
> @POST
> @Produces(MediaType.TEXT_PLAIN)
> @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
> public String login(@Context HttpServletRequest request) {
> String name = request.getParameter("name");
> System.out.println("name : " + name); // The name is null
> if("test".equals(name)) {
> return "SUCCESS";
> }
> return "FAIL";
> }
> }
> {code}
> == Spring config file ==
> {code:xml}
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> === web.xml ===
> {code:xml}
> 
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
> version="3.0"
> metadata-complete="false">
> 
> contextConfigLocation
> 
> classpath*:spring/spring-*.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
> 
> CXFServlet
> 
> org.apache.cxf.transport.servlet.CXFServlet
> 
> 
> CXFServlet
> /services/*
> 
> 
> {code}
> === Test html file ===
> {code:xml}
> 
> 
> 
>   
> 
> 
> http://localhost:8080/cxf/services/login";>
>   name:
> 
> submit
> 
> function visit() {
>   document.getElementById("fm").submit();
> }
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread carvin (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493444#comment-14493444
 ] 

carvin edited comment on CXF-6348 at 4/14/15 2:05 AM:
--

Thanks a lot for your reply, and I think the users were more accustomed to use 
the HttpServletRequest  to get the parameters. Would you consider adding this 
feature?



was (Author: carvin):
Thanks a lot for your reply, and I think the users were more accustomed to use 
the HttpServletRequest  to get the parameters. 


> POST data missing in HttpServletRequest
> ---
>
> Key: CXF-6348
> URL: https://issues.apache.org/jira/browse/CXF-6348
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.0.4
> Environment: Tomcat maven plugin 2.2 OR Jetty maven plugin 
> 9.2.10.v20150310
> JDK 1.7.0_60
> CXF 3.0.4 
> Spring 3.2.13.RELEASE
>Reporter: carvin
>
> Code:
> == Service ==
> {code}
> @Path("/login")
> public class LoginService {
> @POST
> @Produces(MediaType.TEXT_PLAIN)
> @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
> public String login(@Context HttpServletRequest request) {
> String name = request.getParameter("name");
> System.out.println("name : " + name); // The name is null
> if("test".equals(name)) {
> return "SUCCESS";
> }
> return "FAIL";
> }
> }
> {code}
> == Spring config file ==
> {code:xml}
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> === web.xml ===
> {code:xml}
> 
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
> version="3.0"
> metadata-complete="false">
> 
> contextConfigLocation
> 
> classpath*:spring/spring-*.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
> 
> CXFServlet
> 
> org.apache.cxf.transport.servlet.CXFServlet
> 
> 
> CXFServlet
> /services/*
> 
> 
> {code}
> === Test html file ===
> {code:xml}
> 
> 
> 
>   
> 
> 
> http://localhost:8080/cxf/services/login";>
>   name:
> 
> submit
> 
> function visit() {
>   document.getElementById("fm").submit();
> }
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread Sergey Beryozkin (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493469#comment-14493469
 ] 

Sergey Beryozkin commented on CXF-6348:
---

Hi, unlikely unless I get a confirmation from spec leads it is needed. JAX-RS 
message body readers are not invoked if a method signature has no parameter 
representing a payload, and without it a JAX-RS runtime would need to do some 
very specific exceptions. Besides, unless really needed, Servlet API should 
ideally be hidden. I'm not sure the spec will want to do a specific exception 
around this case.

 

> POST data missing in HttpServletRequest
> ---
>
> Key: CXF-6348
> URL: https://issues.apache.org/jira/browse/CXF-6348
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.0.4
> Environment: Tomcat maven plugin 2.2 OR Jetty maven plugin 
> 9.2.10.v20150310
> JDK 1.7.0_60
> CXF 3.0.4 
> Spring 3.2.13.RELEASE
>Reporter: carvin
>
> Code:
> == Service ==
> {code}
> @Path("/login")
> public class LoginService {
> @POST
> @Produces(MediaType.TEXT_PLAIN)
> @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
> public String login(@Context HttpServletRequest request) {
> String name = request.getParameter("name");
> System.out.println("name : " + name); // The name is null
> if("test".equals(name)) {
> return "SUCCESS";
> }
> return "FAIL";
> }
> }
> {code}
> == Spring config file ==
> {code:xml}
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> === web.xml ===
> {code:xml}
> 
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
> version="3.0"
> metadata-complete="false">
> 
> contextConfigLocation
> 
> classpath*:spring/spring-*.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
> 
> CXFServlet
> 
> org.apache.cxf.transport.servlet.CXFServlet
> 
> 
> CXFServlet
> /services/*
> 
> 
> {code}
> === Test html file ===
> {code:xml}
> 
> 
> 
>   
> 
> 
> http://localhost:8080/cxf/services/login";>
>   name:
> 
> submit
> 
> function visit() {
>   document.getElementById("fm").submit();
> }
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CXF-6348) POST data missing in HttpServletRequest

2015-04-13 Thread carvin (JIRA)

[ 
https://issues.apache.org/jira/browse/CXF-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493501#comment-14493501
 ] 

carvin commented on CXF-6348:
-

Hi, I got it , thanks very much.

> POST data missing in HttpServletRequest
> ---
>
> Key: CXF-6348
> URL: https://issues.apache.org/jira/browse/CXF-6348
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.0.4
> Environment: Tomcat maven plugin 2.2 OR Jetty maven plugin 
> 9.2.10.v20150310
> JDK 1.7.0_60
> CXF 3.0.4 
> Spring 3.2.13.RELEASE
>Reporter: carvin
>
> Code:
> == Service ==
> {code}
> @Path("/login")
> public class LoginService {
> @POST
> @Produces(MediaType.TEXT_PLAIN)
> @Consumes(MediaType.APPLICATION_FORM_URLENCODED)
> public String login(@Context HttpServletRequest request) {
> String name = request.getParameter("name");
> System.out.println("name : " + name); // The name is null
> if("test".equals(name)) {
> return "SUCCESS";
> }
> return "FAIL";
> }
> }
> {code}
> == Spring config file ==
> {code:xml}
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> === web.xml ===
> {code:xml}
> 
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd";
> version="3.0"
> metadata-complete="false">
> 
> contextConfigLocation
> 
> classpath*:spring/spring-*.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
> 
> CXFServlet
> 
> org.apache.cxf.transport.servlet.CXFServlet
> 
> 
> CXFServlet
> /services/*
> 
> 
> {code}
> === Test html file ===
> {code:xml}
> 
> 
> 
>   
> 
> 
> http://localhost:8080/cxf/services/login";>
>   name:
> 
> submit
> 
> function visit() {
>   document.getElementById("fm").submit();
> }
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)