[jira] [Created] (CXF-3421) HTTP conduit settigs not used fro downloading WSDL
HTTP conduit settigs not used fro downloading WSDL -- Key: CXF-3421 URL: https://issues.apache.org/jira/browse/CXF-3421 Project: CXF Issue Type: Bug Components: Transports Affects Versions: 2.3.3 Environment: CXF client on Jetty, Java 6. WS server in .NET NTLM secured. Reporter: frantisek.ko...@gmail.com Priority: Critical I have WS on server with NTLM secured HTTP connection. If wsdlLocation is set, CXF tries to download WSDL but does not take HTTP conduit settings into account. Server returned HTTP response code: 401 for URL: http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl WSDL is on location http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl"; And I use service address as http-conduit name like http://172.16.55.55:555/WebServices/WebServiceABC.asmx"; This does not work NAME PASSWORD This works (but does not try to download WSDL) NAME PASSWORD -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3421) HTTP conduit settigs not used fro downloading WSDL
[
https://issues.apache.org/jira/browse/CXF-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011129#comment-13011129
]
Freeman Fang commented on CXF-3421:
---
Hi,
How about you use {WSDL Namespace}portName.http-conduit style for
http-conf:conduit name instead to see if it helps?
The name includes the service's namespace, the WSDL port name (as found in the
wsdl:service section of the WSDL), and ".http-conduit". It follows this
template: "{WSDL Namespace}portName.http-conduit". Note: it's the PORT name,
not the service name. Thus, it's likely something like "MyServicePort", not
"MyService". If you are having trouble getting the template to work, another
(temporary) option for the name value is simply "*.http-conduit".
Freeman
> HTTP conduit settigs not used fro downloading WSDL
> --
>
> Key: CXF-3421
> URL: https://issues.apache.org/jira/browse/CXF-3421
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.3.3
> Environment: CXF client on Jetty, Java 6. WS server in .NET NTLM
> secured.
>Reporter: frantisek.ko...@gmail.com
>Priority: Critical
>
> I have WS on server with NTLM secured HTTP connection. If wsdlLocation is
> set, CXF tries to download WSDL but does not take HTTP conduit settings into
> account. Server returned HTTP response code: 401 for URL:
> http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl
> WSDL is on location
> wsdlLocation="http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl";
> And I use service address as http-conduit name like
> name="http://172.16.55.55:555/WebServices/WebServiceABC.asmx";
> This does not work
> serviceClass="SERVICE_CLASS"
> wsdlLocation="WSDL_LOCATION"
> serviceName="s:SERVICE_NAME"
> xmlns:s="SERVICE_NAMESPACE"
> >
>
> name="SERVICE_ADDRESS">
> ConnectionTimeout="31234" />
>
> NAME
> PASSWORD
>
>
> This works (but does not try to download WSDL)
> name="SERVICE_NAME"
> address="SERVICE_ADDRESS"
> serviceClass="SERVICE_CLASS"
> >
>
> name="SERVICE_ADDRESS">
> ConnectionTimeout="31234" />
>
> NAME
> PASSWORD
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Vitoria updated CXF-3418: -- Attachment: (was: JaxrsTransactional v1.0.part1.rar) > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Vitoria updated CXF-3418: -- Attachment: (was: JaxrsTransactional v1.0.part2.rar) > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Vitoria updated CXF-3418: -- Attachment: JaxrsTransactional.part1.rar > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Vitoria updated CXF-3418: -- Attachment: JaxrsTransactional.part2.rar > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar, > JaxrsTransactional.part2.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011135#comment-13011135 ] Ivan Vitoria commented on CXF-3418: --- Hi Sergey, I apologize for attaching a NB project. Now, you can find a war file with its source code. I'm not familiarized with Maven yet but definitely i'm going to learn how it works as soon as possible. Thanks, Ivan > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar, > JaxrsTransactional.part2.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3421) HTTP conduit settigs not used fro downloading WSDL
[
https://issues.apache.org/jira/browse/CXF-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011144#comment-13011144
]
frantisek.ko...@gmail.com commented on CXF-3421:
I tried it. Both of them ("{WSDL Namespace}portName.http-conduit" and
"*.http-conduit") work for service method invocations. But none of them for
downloading the WSDL.
> HTTP conduit settigs not used fro downloading WSDL
> --
>
> Key: CXF-3421
> URL: https://issues.apache.org/jira/browse/CXF-3421
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.3.3
> Environment: CXF client on Jetty, Java 6. WS server in .NET NTLM
> secured.
>Reporter: frantisek.ko...@gmail.com
>Priority: Critical
>
> I have WS on server with NTLM secured HTTP connection. If wsdlLocation is
> set, CXF tries to download WSDL but does not take HTTP conduit settings into
> account. Server returned HTTP response code: 401 for URL:
> http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl
> WSDL is on location
> wsdlLocation="http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl";
> And I use service address as http-conduit name like
> name="http://172.16.55.55:555/WebServices/WebServiceABC.asmx";
> This does not work
> serviceClass="SERVICE_CLASS"
> wsdlLocation="WSDL_LOCATION"
> serviceName="s:SERVICE_NAME"
> xmlns:s="SERVICE_NAMESPACE"
> >
>
> name="SERVICE_ADDRESS">
> ConnectionTimeout="31234" />
>
> NAME
> PASSWORD
>
>
> This works (but does not try to download WSDL)
> name="SERVICE_NAME"
> address="SERVICE_ADDRESS"
> serviceClass="SERVICE_CLASS"
> >
>
> name="SERVICE_ADDRESS">
> ConnectionTimeout="31234" />
>
> NAME
> PASSWORD
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-3422) 'Cannot find target method' when certain hex-encoded characters are used in @PathParam in GET requests
'Cannot find target method' when certain hex-encoded characters are used in
@PathParam in GET requests
--
Key: CXF-3422
URL: https://issues.apache.org/jira/browse/CXF-3422
Project: CXF
Issue Type: Bug
Components: JAX-RS
Affects Versions: 2.3.3, 2.3.1
Environment: Tomcat 6
Reporter: Karel Vlcek
Priority: Minor
I have following simple JAX-RS service:
{code}
public interface RootService {
@Path("data1")
public DataService getDataService();
}
public interface DataService {
@GET
@Path("data2/{id}")
public Data getData(@PathParam("id") String id);
}
{code}
All works correctly as long as URL contains in position of @PathParam("id")
ASCII characters and digits or hex-encoded spaces. These URLs work:
GET /root/data1/data2/1
GET /root/data1/data2/AAA2BBB
GET /root/data1/data2/1%202
However, when URL on position of the parameter {id} contains certain
hex-encoded characters other than space (1%202), like in this URL (this example
contains digit '1' followed by 'latin capital letter d with caron'):
GET /root/data1/data2/1%C4%8E
I'll get following exception:
{noformat}
javax.ws.rs.WebApplicationException
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
at
org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:149)
at
org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:662)
{noformat}
{code}
//
// Simple implementations - just to complete the example...
public class RootServiceImpl implements RootService {
@Override
public StaticDataService getDataService() {
return new DataServiceImpl();
}
}
public class DataServiceImpl implements DataService {
@Override
public Data getData(final String id) {
// ...
}
}
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3422) 'Cannot find target method' when certain hex-encoded characters are used in @PathParam in GET requests
[
https://issues.apache.org/jira/browse/CXF-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karel Vlcek updated CXF-3422:
-
Description:
I have following simple JAX-RS service:
{code}
public interface RootService {
@Path("data1")
public DataService getDataService();
}
public interface DataService {
@GET
@Path("data2/{id}")
public Data getData(@PathParam("id") String id);
}
{code}
All works correctly as long as URL contains in position of @PathParam("id")
ASCII characters and digits or hex-encoded spaces. These URLs work:
GET /root/data1/data2/1
GET /root/data1/data2/AAA2BBB
GET /root/data1/data2/1%202
However, when URL on position of the parameter {id} contains certain
hex-encoded characters other than space (1%202), like in this URL (this example
contains digit '1' followed by 'latin capital letter d with caron'):
GET /root/data1/data2/1%C4%8E
I'll get following exception:
{noformat}
javax.ws.rs.WebApplicationException
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
at
org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:149)
at
org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:662)
{noformat}
{code}
//
// Simple implementations - just to complete the example...
public class RootServiceImpl implements RootService {
@Override
public DataService getDataService() {
return new DataServiceImpl();
}
}
public class DataServiceImpl implements DataService {
@Override
public Data getData(final String id) {
// ...
}
}
{code}
was:
I have following simple JAX-RS service:
{code}
public interface RootService {
@Path("data1")
public DataService getDataService();
}
public interface DataService {
@GET
@Path("data2/{id}")
public Data getData(@PathParam("id") String id);
}
{code}
All works correctly as long as URL contains in position of @PathParam("id")
ASCII characters and digits or hex-encoded spaces. These URLs work:
GET /root/data1/data2/1
GET /root/data1/data2/AAA2BBB
GET /root/data1/data2/1%202
However, when URL on position of the parameter {id} contains certain
hex-encoded characters other than space (1%202), like in this URL (this example
contains digit '1' followed by 'latin capital letter d with caron'):
GET /root/data1/data2/1%C4%8E
I'll get following exception:
{noformat}
javax.ws.rs.WebApplicationException
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
at
org.apache.cxf.ph
[jira] [Updated] (CXF-3422) 'Cannot find target method' when certain hex-encoded characters are used in @PathParam in GET requests
[
https://issues.apache.org/jira/browse/CXF-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karel Vlcek updated CXF-3422:
-
Description:
I have following simple JAX-RS service:
{code}
public interface RootService {
@Path("data1")
public DataService getDataService();
}
public interface DataService {
@GET
@Path("data2/{id}")
public Data getData(@PathParam("id") String id);
}
{code}
All works correctly as long as URL contains in position of @PathParam("id")
ASCII characters and digits or hex-encoded spaces. These URLs work:
GET /root/data1/data2/1
GET /root/data1/data2/AAA2BBB
GET /root/data1/data2/1%202
However, when URL on position of the parameter {id} contains certain
hex-encoded characters other than space (%20), like in this URL (this example
contains digit '1' followed by 'latin capital letter d with caron'):
GET /root/data1/data2/1%C4%8E
I'll get following exception:
{noformat}
javax.ws.rs.WebApplicationException
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
at
org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:149)
at
org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:662)
{noformat}
{code}
//
// Simple implementations - just to complete the example...
public class RootServiceImpl implements RootService {
@Override
public DataService getDataService() {
return new DataServiceImpl();
}
}
public class DataServiceImpl implements DataService {
@Override
public Data getData(final String id) {
// ...
}
}
{code}
was:
I have following simple JAX-RS service:
{code}
public interface RootService {
@Path("data1")
public DataService getDataService();
}
public interface DataService {
@GET
@Path("data2/{id}")
public Data getData(@PathParam("id") String id);
}
{code}
All works correctly as long as URL contains in position of @PathParam("id")
ASCII characters and digits or hex-encoded spaces. These URLs work:
GET /root/data1/data2/1
GET /root/data1/data2/AAA2BBB
GET /root/data1/data2/1%202
However, when URL on position of the parameter {id} contains certain
hex-encoded characters other than space (1%202), like in this URL (this example
contains digit '1' followed by 'latin capital letter d with caron'):
GET /root/data1/data2/1%C4%8E
I'll get following exception:
{noformat}
javax.ws.rs.WebApplicationException
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
at
org.apache.cxf.phas
[jira] [Created] (CXF-3423) Better support for adding documentation to auto-generated WADLs
Better support for adding documentation to auto-generated WADLs --- Key: CXF-3423 URL: https://issues.apache.org/jira/browse/CXF-3423 Project: CXF Issue Type: Improvement Components: JAX-RS Affects Versions: 2.3.3, 2.4 Reporter: Sergey Beryozkin Assignee: Sergey Beryozkin Fix For: 2.4 It is not possible at the moment to add WADL doc extensions to response representation elements. WADL request and response elements can not be documented as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3421) HTTP conduit settigs not used fro downloading WSDL
[
https://issues.apache.org/jira/browse/CXF-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011186#comment-13011186
]
Daniel Kulp commented on CXF-3421:
--
The "{WSDL Namespace}portName" for would never work for downloading the wsdl as
the portName is unknown at that point.
Use:
{code:xml}
http://172.16.55.55:555/WebServices/WebServiceABC.asmx.*";
{code}
The "name" is a regex that needs to match the full url of what is being asked.
The ".*" at the end would allow it to match the ?wsdl as well. You could
also do:
{code:xml}
http://172.16.55.55:555/.*";
{code}
To make it match all URL's at that host/port.
> HTTP conduit settigs not used fro downloading WSDL
> --
>
> Key: CXF-3421
> URL: https://issues.apache.org/jira/browse/CXF-3421
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.3.3
> Environment: CXF client on Jetty, Java 6. WS server in .NET NTLM
> secured.
>Reporter: frantisek.ko...@gmail.com
>Priority: Critical
>
> I have WS on server with NTLM secured HTTP connection. If wsdlLocation is
> set, CXF tries to download WSDL but does not take HTTP conduit settings into
> account. Server returned HTTP response code: 401 for URL:
> http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl
> WSDL is on location
> wsdlLocation="http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl";
> And I use service address as http-conduit name like
> name="http://172.16.55.55:555/WebServices/WebServiceABC.asmx";
> This does not work
> serviceClass="SERVICE_CLASS"
> wsdlLocation="WSDL_LOCATION"
> serviceName="s:SERVICE_NAME"
> xmlns:s="SERVICE_NAMESPACE"
> >
>
> name="SERVICE_ADDRESS">
> ConnectionTimeout="31234" />
>
> NAME
> PASSWORD
>
>
> This works (but does not try to download WSDL)
> name="SERVICE_NAME"
> address="SERVICE_ADDRESS"
> serviceClass="SERVICE_CLASS"
> >
>
> name="SERVICE_ADDRESS">
> ConnectionTimeout="31234" />
>
> NAME
> PASSWORD
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3423) Better support for adding documentation to auto-generated WADLs
[ https://issues.apache.org/jira/browse/CXF-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-3423. --- Resolution: Fixed > Better support for adding documentation to auto-generated WADLs > --- > > Key: CXF-3423 > URL: https://issues.apache.org/jira/browse/CXF-3423 > Project: CXF > Issue Type: Improvement > Components: JAX-RS >Affects Versions: 2.3.3, 2.4 >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin > Fix For: 2.4 > > > It is not possible at the moment to add WADL doc extensions to response > representation elements. WADL request and response elements can not be > documented as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3421) HTTP conduit settigs not used fro downloading WSDL
[ https://issues.apache.org/jira/browse/CXF-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011197#comment-13011197 ] frantisek.ko...@gmail.com commented on CXF-3421: Yes Daniel I think it should work the way you suggested but it does not. When using wsdlLocation, it tries to download WSDL without authentication. So I reported a bug. > HTTP conduit settigs not used fro downloading WSDL > -- > > Key: CXF-3421 > URL: https://issues.apache.org/jira/browse/CXF-3421 > Project: CXF > Issue Type: Bug > Components: Transports >Affects Versions: 2.3.3 > Environment: CXF client on Jetty, Java 6. WS server in .NET NTLM > secured. >Reporter: frantisek.ko...@gmail.com >Priority: Critical > > I have WS on server with NTLM secured HTTP connection. If wsdlLocation is > set, CXF tries to download WSDL but does not take HTTP conduit settings into > account. Server returned HTTP response code: 401 for URL: > http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl > WSDL is on location > wsdlLocation="http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl"; > And I use service address as http-conduit name like > name="http://172.16.55.55:555/WebServices/WebServiceABC.asmx"; > This does not work > serviceClass="SERVICE_CLASS" > wsdlLocation="WSDL_LOCATION" > serviceName="s:SERVICE_NAME" > xmlns:s="SERVICE_NAMESPACE" > > > > name="SERVICE_ADDRESS"> > ConnectionTimeout="31234" /> > > NAME > PASSWORD > > > This works (but does not try to download WSDL) > name="SERVICE_NAME" > address="SERVICE_ADDRESS" > serviceClass="SERVICE_CLASS" > > > > name="SERVICE_ADDRESS"> > ConnectionTimeout="31234" /> > > NAME > PASSWORD > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3186) Update to latest JAXB version 2.2.3 from 2.2.2
[ https://issues.apache.org/jira/browse/CXF-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011257#comment-13011257 ] Stephen Souness commented on CXF-3186: -- The related bug that you refer to appears to have been resolved, should this issue be updated accordingly? > Update to latest JAXB version 2.2.3 from 2.2.2 > -- > > Key: CXF-3186 > URL: https://issues.apache.org/jira/browse/CXF-3186 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.3.1 >Reporter: Gary D. Gregory > > Update to latest JAXB version 2.2.3 from 2.2.2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CXF-3186) Update to latest JAXB version 2.2.3 from 2.2.2
[ https://issues.apache.org/jira/browse/CXF-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011257#comment-13011257 ] Stephen Souness edited comment on CXF-3186 at 3/25/11 4:13 PM: --- The related issue that you refer to appears to have been resolved, should this issue be updated accordingly? was (Author: sounie): The related bug that you refer to appears to have been resolved, should this issue be updated accordingly? > Update to latest JAXB version 2.2.3 from 2.2.2 > -- > > Key: CXF-3186 > URL: https://issues.apache.org/jira/browse/CXF-3186 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.3.1 >Reporter: Gary D. Gregory > > Update to latest JAXB version 2.2.3 from 2.2.2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3422) 'Cannot find target method' when certain hex-encoded characters are used in @PathParam in GET requests
[
https://issues.apache.org/jira/browse/CXF-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011260#comment-13011260
]
Sergey Beryozkin commented on CXF-3422:
---
Hi, thanks for the detailed info.
Works for me, I updated the existing system test and it works fine. It is Jetty
based.
2.3.3 has a brittle workaround to do with the fact HttpServletRequest loses
matrix parameters on the last path segment. It was removed in 2.3.4-SNAPSHOT
and all the encoded URI should be supported properly.
Can you please try 2.3.4-SNAPHOT [1] and let me know if this issue persists ? I
hope you will confirm it has been resolved :-)
thanks, Sergey
[1]
http://repository.apache.org/snapshots/org/apache/cxf/apache-cxf/2.3.4-SNAPSHOT/
> 'Cannot find target method' when certain hex-encoded characters are used in
> @PathParam in GET requests
> --
>
> Key: CXF-3422
> URL: https://issues.apache.org/jira/browse/CXF-3422
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.3.1, 2.3.3
> Environment: Tomcat 6
>Reporter: Karel Vlcek
>Priority: Minor
>
> I have following simple JAX-RS service:
> {code}
> public interface RootService {
> @Path("data1")
> public DataService getDataService();
> }
> public interface DataService {
> @GET
> @Path("data2/{id}")
> public Data getData(@PathParam("id") String id);
> }
> {code}
> All works correctly as long as URL contains in position of @PathParam("id")
> ASCII characters and digits or hex-encoded spaces. These URLs work:
> GET /root/data1/data2/1
> GET /root/data1/data2/AAA2BBB
> GET /root/data1/data2/1%202
> However, when URL on position of the parameter {id} contains certain
> hex-encoded characters other than space (%20), like in this URL (this example
> contains digit '1' followed by 'latin capital letter d with caron'):
> GET /root/data1/data2/1%C4%8E
> I'll get following exception:
> {noformat}
> javax.ws.rs.WebApplicationException
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
> at
> org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:149)
> at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> {code}
> //
> // Simple implementations - just to complete the example...
> public class RootServiceImpl implements RootService {
> @Override
> public DataService getDataService() {
> return new DataServiceImpl();
> }
> }
> public class DataServiceImpl implements DataServi
[jira] [Commented] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011268#comment-13011268 ] Sergey Beryozkin commented on CXF-3418: --- Hi Ivan - no probs at all - thanks for attaching the war > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar, > JaxrsTransactional.part2.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[
https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011336#comment-13011336
]
Sergey Beryozkin commented on CXF-3418:
---
Hi Ivan
Debugging this project is not easy :-). Can you please give me a favor and try
the following:
you have
public class GenericRestServiceImpl {
@Context
public void setUriInfo(UriInfo uriInfo) {}
}
Can you please do the following:
1. Add interface say IContext:
public interface IContext {
@Context
void setUriInfo(UriInfo uriInfo);
}
}
and then
public class GenericRestServiceImpl implements IRestService, IContext{
public void setUriInfo(UriInfo uriInfo) {}
}
Can you try it please ?
> Transactional JAX-RS Service (Spring 3 + Hibernate 3)
> -
>
> Key: CXF-3418
> URL: https://issues.apache.org/jira/browse/CXF-3418
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.3.2
>Reporter: Ivan Vitoria
>Priority: Critical
> Attachments: JaxrsTransactional.part1.rar,
> JaxrsTransactional.part2.rar
>
>
> Hello,
> I have some JAX-RS servers configured through Spring. Also, i'm using
> Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no
> problem when I add the @Transactional annotation to the DAO layer, but i
> would like to have the REST methods in the same transaction, so i've annoated
> the services. But I can't do it, neither annotating the interface nor the
> classes. A ServiceConstructionException is throwed as soon as I add the
> @Transactional to the service...
> A sample NetBeans project is attached.
> Thanks in advance
> Ivan
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3379) @Context fails to inject Application instance
[ https://issues.apache.org/jira/browse/CXF-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011441#comment-13011441 ] Ben Noordhuis commented on CXF-3379: Thanks for the heads up, Sergey! > @Context fails to inject Application instance > - > > Key: CXF-3379 > URL: https://issues.apache.org/jira/browse/CXF-3379 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.3 >Reporter: Ben Noordhuis >Assignee: Sergey Beryozkin > Fix For: 2.4, 2.3.4 > > > Quoting JSR 311: > "The instance of the application-supplied Application subclass can be > injected into a class field or method parameter using the @Context > annotation. Access to the Application subclass instance allows configuration > information to be centralized in that class. Note that this cannot be > injected into the Application subclass itself since this would create a > circular dependency." > JAXRSUtils.createContextValue() doesn't handle this. This bug exists in 2.3.x > and HEAD. > I'd submit a patch but I don't know where (or if) the Application class is > registered after it's instantiated by CXFNonSpringJaxrsServlet. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
