Thanks for the pointer.
On Tue, Nov 11, 2008 at 8:23 AM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> The class to look at is PROBABLY the
> org.apache.cxf.jaxb.io.DataWriterImpl
> The code is a little different on trunk as I've been working on getting it
> able to use the jaxb implementation built
Hi,
I am trying to upgrade to version 2.1.2 of the cxf-codegen-plugin in my
mule/maven project.
cxf-codegen-plugin version 2.0.6 and 2.1 works fine.
With version 2.1.1, 2.1.2 and 2.1.3 i get a
javax.xml.transform.TransformerFactoryConfigurationError: Provider
org.apache.xalan.processor.Transfo
May be I sound stupid but I am trying to learn web services and CXF on hands,
please bear with me :-(
I am seeing every message in/out bound twice in log, can I tweak it, it is
pretty confusing, the only difference is b/w headers.
I call
Okay I found out the reason, I was loading cxf.xml before publishing the
service.
Now the question remains that how can I redirect the log to some log file. May
be cxf:bus has some properties.
Thanks,
Petr
--- On Wed, 11/12/08, Petr V. <[EMAIL PROTECTED]> wrote:
From: Petr V. <[EMAIL PROTECT
So I loaded explicitly cxf.xml in my code and now I am getting null pointer
exception when I am trying to publish the web service.
Here is my cxf.xml
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:cxf="http://cxf.apache.org/
Hi,
I'm using Metro 1.3 with JDK 1.5.x.
I need a solution for streaming large messages - currently in my
solution - we stream large messages by using the Provider API -
dispatching the XML file from the client to the server side.
However on the server side we receive a StaxSource object - and i
Hi,
I'm using Metro 1.3 with JDK 1.5.x.
I need a solution for streaming large messages - currently in my
solution - we stream large messages by using the Provider API -
dispatching the XML file from the client to the server side.
However on the server side we receive a StaxSource object - and i
Thanks Erik but how are you integrating this with your service. Can you please
eloborate more.
I have this cxf.xml in my class path
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://www.springframework.org/sch
This works for me:
Taken from here: http://cwiki.apache.org/CXF20DOC/features.html
--Erik
-Original Message-
From: Petr V. [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 4:40 PM
To: users@cxf.apache.org
Subject: Re: How to Enable L
Thanks Glex for the reply.
Yeah I did look at that page and was able to configured logging via programming
includes but I want to do via config files.
I have included cxf-2.1.1.jar file in my class path so I do not know what to do
when that wiki says I need to change settings in /etc/logging.pr
http://cwiki.apache.org/CXF20DOC/debugging.html ?
Petr V. wrote:
>
> So I am trying to figure it out how could I enable logging via
> configuration file
>
--
View this message in context:
http://www.nabble.com/How-to-Enable-Logging-of-In-Out-Bound-Soap-Messages-tp20449139p20449787.html
Sent
The Metro guide seems to suggest the default verifier is a little bit more
intelligent than that:
https://metro.dev.java.net/guide/Security_Mechanisms.html#Transport_Security__SSL__Workaround
But perhaps this is a result of switching from JDK 5 to 6? Anyway, the
workaround they have above probab
Perhaps my Maven POM files might be something you can use:
http://www.jroller.com/gmazza/date/20080417#WFstep3
HTH,
Glen
Kent Narling wrote:
>
> Hi!
> I am trying to make a CXF webservice package in maven.
>
--
View this message in context:
http://www.nabble.com/Creating-CXF-war-file...-h
So I am trying to figure it out how could I enable logging via configuration
file
Right now, I have following code
String address1 = "http://localhost:9000/service1";;
Service1 implementor1 = new Service1();EndpointImpl myEndpoint1 =
(EndpointImpl) Endpoint.publish(address1, implementor1);
On Tuesday 11 November 2008 4:11:45 pm Glen Mazza wrote:
> Hmmm...I'm sure I had tested that. I wonder if my 2.0.x change was *not*
> ported to the 2.1 branch?
Looking back at the change history, your changes seem to add the "AlwaysTrue"
verifier only if DisableCNCheck flag is true. Previous t
>
> javax.xml
> jaxb-api
> 2.1
>
>
> com.sun.xml.bind
> jaxb-xjc
> 2.0.3
> compile
>
>
> com.sun.xml.bind
> jaxb-impl
> 2.0.3
>
>
Umm... jaxb-api is 2.1, but you are including 2.0.x versions of jaxb-impl
and xjc That definitely won't work.
I would recommend 2.1 api jar and 2.1
Hi!
I am trying to make a CXF webservice package in maven.
But it seems SO darn difficult to get the right dependencies!
Either classes are missing or I get stupid collissions...
Anyone have tips what dependencies to declare to be able to deploy a CXF war
file on a fresh installed tomcat (5.5.27
Hmmm...I'm sure I had tested that. I wonder if my 2.0.x change was *not*
ported to the 2.1 branch?
Glen
dkulp wrote:
>
>
> Looking at the decompiled source for the "DefaultHostnameVerifier", it
> literally just does a "return false;". Thus, I don't see how it's
> possible
> to do any SSL
Looking at the decompiled source for the "DefaultHostnameVerifier", it
literally just does a "return false;". Thus, I don't see how it's possible
to do any SSL things with host bound certs right now without the
DisableCNCheck thing.It looks like we need to write a new
HostNameVerifier th
I am trying to use apache-cxf 's REST service. However, jax-rs seems to
be doing something bad to my URLs .. I only get the first query
parameter that is passed to the request. Is this a bug or am I missing
some configuration ?
Eg. If I pass
/svc/something?param1=value1¶m2=value2
When print out
We recently upgraded to CXF 2.1.3 from 2.1.2. After the upgrade we noticed
that JMS conduits with a reply to queue were not always working if we had
multiple instances running. I didn't dive into the problem real deep, but
rather just removed the reply to queue config so that it would use a
tempor
If you can check the CXF source code (I don't have it with me immediately,
but search the source code for the error message you're getting to determine
the class) -- you can place debugging statements on what CXF thinks the
hostname URL and the CN is to determine why it is failing on you. Perhaps
On Tuesday 11 November 2008 12:26:38 pm Glen Mazza wrote:
> BTW, anyone have the answer to my unphrased question--when referring to a
> client-side endpoint, when is the ".http-conduit" suffix needed, and does
> its presence have any correlation to the value of the "createdFromAPI"
> attribute?
Th
On Tuesday 11 November 2008 12:31:32 pm Harry van Rijn wrote:
> Hi,
>
> It looks like that properties in the http:conduit element are NOT resolved.
> Is there a way out?
This SHOULD be working in CXF 2.1.3, maybe 2.1.2. What version of CXF are
you using?
Dan
> I want to refer to configuratio
I understand why it was done, but the problem is I cannot get ssl with cxf to
work unless the flag is set to true, which I do not want to do in a
production environment.
Glen Mazza wrote:
>
> I'm unsure what the problem is. I had done that last March[1] after
> agreement with the team.
>
> G
I'm unsure what the problem is. I had done that last March[1] after
agreement with the team.
Glen
[1] http://www.jroller.com/gmazza/date/20080329
wonderingWV wrote:
>
> The common name on the cert and the hostName of the url match up so I not
> sure why I continue to receive this error. Any
I'm trying to get ssl to work with CXF, but continue to get
Caused by: java.io.IOException: The https URL hostname does not match the
Common
Name (CN) on the server certificate. To disable this check (NOT
recommended fo
r production) set the CXF client TLS configuration property "disableCNChe
On Monday 10 November 2008 1:15:54 pm Brad O'Hearne wrote:
> Well, I guess throw the idea around with the other developers. If I'm
> not an intrusion, I'd be happy to pitch in when I can.
Patches to problems are never an intrusion. New ideas and discussions are
also great. That's how a project
Robin,
The second bean definition was added because in one of the Spring versions
that we were using (2.5.4 I think, maybe 2.5.2), it couldn't find the bean to
inject. The injector was just doing field.getClass().getName() to determine
the bean name. We didn't have a bean of that name and
Hi,
It looks like that properties in the http:conduit element are NOT resolved.
Is there a way out? I want to refer to configuration files in the JBoss config
directoy:
Here is my beans containing file:
http://www.springframework.org/sc
BTW, anyone have the answer to my unphrased question--when referring to a
client-side endpoint, when is the ".http-conduit" suffix needed, and does
its presence have any correlation to the value of the "createdFromAPI"
attribute?
Thanks,
Glen
Glen Mazza wrote:
>
> Thanks, I'll try again. I pu
Hi Sergey
>Would you like your interceptor be invoked before or
after JAXRSInInterceptor has been invoked ?
After
>What stage you're using ?
Not sure
>Also, can you elaborate a bit more on how you specify interceptors using
annotations ?
This is the annotation for the class
@OutInterceptors
That looks like a bug. Can you log a JIRA and attach the wsdl?
https://issues.apache.org/jira/browse/CXF
Dan
On Tuesday 11 November 2008 9:48:46 am Alexey Zavizionov wrote:
> Hello, list!
>
> I'm generating sources with CXF maven plugin
>
> cxf-codegen-plugin
> 2.1.2
>
> I ha
The class to look at is PROBABLY the
org.apache.cxf.jaxb.io.DataWriterImpl
The code is a little different on trunk as I've been working on getting it
able to use the jaxb implementation built into Java6, but it shouldn't be
hard to follow.
The "com.sun.xml.bind.defaultNamespaceRemap" propert
Sorry, misread "connection pool timeout" for "connection timeout",
apologies for any confusion.
2008/11/11 Andrew Clegg <[EMAIL PROTECTED]>:
> Check out this page, under "Advanced configuration":
>
> http://cwiki.apache.org/CXF20DOC/client-http-transport-including-ssl-support.html
>
> The http-con
CXF uses the JDK HttpURLConnection objects for client side. Thus, any
information pertaining to that that you may google applies.
In particular, it holds a pool of 5 connections, but only holds each
connection open for 5 seconds beyond the last use. What's worse is it's not
exactly co
If you use wsdl first and run wsdl2java, you probably don't need the asm jar.
Accessing the parts from the wrapper objects will be done by the slightly
slower reflection code, but that should be fine.
If you do java first, you can remove it if you add run java2ws with
the -wrapperbean flag t
Hello, list!
I'm generating sources with CXF maven plugin
cxf-codegen-plugin
2.1.2
I have just noticed that I get incorrect portName annotation.
=== service.wsdl =
...
...
http://my.service:8082/WSRPService"/>
http://
Check out this page, under "Advanced configuration":
http://cwiki.apache.org/CXF20DOC/client-http-transport-including-ssl-support.html
The http-conf:client element is where most of this stuff lives.
The easiest way to set global properties is by using this syntax:
However if you use JAX-WS Pr
Hi
In axis client to a webservice, we can configure the number of connections
and the connection pool timeout as below
System.setProperty("axis.http.client.maximum.total.connections",
"20");
System.setProperty("axis.http.client.connection.pool.timeout", "0");
Is there a way the
Hi All,
I encountered this by accident. Here is the scenario:
expected payload:
http://some.namespace/";>
... more here
submitted payload:
http://accounts.some.namespace/";>
... more details here
On the server side, I see the error as:
javax.xml.bind.UnmarshalException: unexpected element
(u
Vi Da wrote:
> I am running into an issue where I have to use a legacy library which uses
> cglib-full-2.0.2.jar and comes in conflict with asm-2.2.3.jar.
If you can use cglib-nodep instead then you will be able to include asm
2.2.3 and it will all work.
Ian
42 matches
Mail list logo
