I tried more options tonight.
With the parent last classloader, even when I add xalan, xercesImpl
and xml-apis' from within xalan 2.7.1 bin to WEB-INF/lib, I still get
this same error (DocumentBuilderFactory class cast exception)
In websphere 7.0, there isn't a washome/java/jre/lib/endorsed, but
it is possible in CXF to disable EMAILADRESS encoding
When my CXF app sign a response, this is the output:
CN=Pepe
Certificate
Authority,C=UY,ST=Montevideo,L=Montevideo,*1.2.840.113549.1.9.1=#161463616e616c65734061616d2d62756c6c2e636f6d*,OU=Proyecto
Pepe,O=Pepr1.2.840.113549.1.9.1=#161463616e616c6
Can you log both of these as bugs in JIRA?
https://issues.apache.org/jira/browse/CXF
A test case (or even a patch) would be great as well. :-)
Dan
On Tuesday, December 27, 2011 5:03:30 PM David Karlsen wrote:
> I also found another regression:
>
> Duplicated option: verbose when I have
> -v
Is this occurring outside of Sonar as well?I have no idea what would
cause this error as you aren't configuring in a classesDirectory. Strange.
Dan
On Tuesday, December 27, 2011 11:02:39 AM Celinio wrote:
> Hi,
> I am getting this error when using the version 2.5.1 of the
> cxf-codegen-p
We have a system test that sends 7 attachments so this definitely should work.
Any chance you can create a small testcase?
Dan
On Friday, December 23, 2011 11:34:34 AM Son Tung Nguyen wrote:
> I'm trying to create a Webservice with MTOM enabled, that accept 2 binary
> files, here's my webmeth
The best bet is to change to using the @Logging annotation we have instead of
the @InInterceptors/@OutInterceptors. The @Logging annotation allows
specifying file URL's for the output.
http://cxf.apache.org/javadoc/latest/org/apache/cxf/annotations/Logging.html
Dan
On Wednesday, December 2
Been trying for a while now.
Can you send me the jar list you have in your project? (minus the custom
ones)
Thanks
Brian
On Dec 28, 2011 7:24 PM, "Mahesh Koli" wrote:
> I don't know if this would help
>
> But I had similar problem when trying to generate java client classes from
> wsdl and one
I don't know if this would help
But I had similar problem when trying to generate java client classes from
wsdl and one of the xml apis where in conflict.
I got around it by trial and error, by traversing through which class it is
expecting and which class is getting loaded that causes that class
I have a resource and a sub resource...
@Path(/user)
@Service
public UserServiceImpl {
@Path("{userId}/contact")
public IContactService getContactService(@PathParam("userId") Long userId);
}
@Service
public ContactServiceImpl {
@POST
public Response addContact(Long userId, Contac
Thanks for replying.
I found your article before, I also followed Thaker's guide, none of
them have solved it.
It is a problem with my list of jars in WEB-INF/lib. Unfortunately, I
just don't know what the correct combination of jars is to make this
work. I've tried to piece it together unsucce
Might this help?
http://www.jroller.com/gmazza/entry/deploying_webservices_on_websphere
Glen
On 12/28/2011 05:56 PM, Brian Hayward wrote:
Hey all,
So far, I've tried a number of things to get the above combination
working with no luck.
* Follow the PDF provided by IBM
* Follow the tips in th
Hi
I need to implement ws security(CXF) with Signature.
The default configuration Issuer Name and Serial Number works fine.
I want to invoke from soap ui with others "key identifier types" like
BinarySecurityToken, x509 or SubjectKeyIdentifier but i didnt find any
documentation.
I tried to set
Hello Sergey
I tested the same with the latest CXF version and it still fails with
following error when I access the URL as follows:
*http://localhost:8080/cxftest/myService/customer/1;customerId=ssn/entitlement*
When I access this URL, it works:
*http://localhost:8080/cxftest/myService/custome
Thanks Jeff, your suggestion worked
--
View this message in context:
http://cxf.547215.n5.nabble.com/Newbie-Question-WARNING-No-root-resource-matching-request-path-has-been-found-tp5098573p5105681.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi all
I m logging my soap in/out xml using the annotations
@InInterceptors(interceptors =
"org.apache.cxf.interceptor.LoggingInInterceptor")
@OutInterceptors(interceptors =
"org.apache.cxf.interceptor.LoggingOutInterceptor")
That works great. requests and response are logged in my application s
Hey all,
So far, I've tried a number of things to get the above combination
working with no luck.
* Follow the PDF provided by IBM
* Follow the tips in this email thread, such as putting neethi,
xmlschema in the JVM endorsed folder
* Parent Last classloader configurations
* Disabling JAX-WS Annota
Thanks Glen,
That helps, too.
Guy
PS I am a big fan of your blog, BTW
On 27-dec-2011, at 19:14, Glen Mazza wrote:
Dan's technically on vacation this week, so perhaps I can answer: Yes[1],
although hardcoding the wsdlLocation makes it less maintainable (can't change
the value without recompi
Yes, Endpoint.publish() takes only one port's endpoint, and so if you
want to have multiple endpoints running simultaneously, you need to have
multiple Endpoint.publish() commands.Alternatively, for Tomcat or
similar deployment, you would declare multiple
elements[1]. As Endpoint.publish(
- Original Message -
From: "Glen Mazza"
To:
Sent: Wednesday, December 28, 2011 9:25 PM
Subject: Re: Does CXF support multiple endpoint for single wsdl now?
> Within the same configuration file, can't you specify two separate
> services, one with each port you wish to activate? That
Within the same configuration file, can't you specify two separate
services, one with each port you wish to activate? That may be CXF's
way of supporting "multiport at runtime".
Glen
On 12/28/2011 04:07 AM, xuhb wrote:
- Original Message -
From: "Willem Jiang"
To:
Sent: Wednesday, De
- Original Message -
From: "Willem Jiang"
To:
Sent: Wednesday, December 28, 2011 4:29 PM
Subject: Re: Does CXF support multiple endpoint for single wsdl now?
> In this case you need to specify the two endpoint and publish them
> separately.
>
Yes, this is the only way I can do; and
In this case you need to specify the two endpoint and publish them
separately.
The port of the wsdl is band to the CXF endpoint, you may need to do
some addition work to check the WSDL if you want to publish the service
from the WSDL automatically.
On 12/28/11 3:53 PM, xuhb wrote:
Thanks wi
Thanks Willem:
I think I haven't explained what I want clearly;
I want CXF to publish a single service with multiply port taking effect
simultaneously at runtime. I am not sure if CXF could or not;
- Original Message -
From: "Willem Jiang"
To:
Sent: Tuesday, December 27, 2011 9:21 PM
23 matches
Mail list logo
