ion and that had the
same error. I'll try to find the original test case and/or look at the
source code.
Thanks,
-Chris W.
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Monday, January 05, 2009 3:00 PM
To: users@cxf.apache.org
Cc: Wolf, Chris (IT)
Subje
ed from the common schema import file, rather then whole
schema.
-Chris W.
-Original Message-
From: Ian Roberts [mailto:i.robe...@dcs.shef.ac.uk]
Sent: Monday, January 05, 2009 11:32 AM
To: users@cxf.apache.org
Subject: Re: CXF query URL for schema-only?
Wolf, Chris (IT) wrote:
&
ly developers of SOAP clients don't need to get into that level of
detail. Note however, your WSDL can import multiple XSD's, so those
would need to be downloaded and parsed as well.
Glen
Wolf, Chris (IT) wrote:
>
> I know there are several special query strings for WSDL and
java:803)
Or did I misunderstand what you were suggesting with "?xsd=MySchema.xsd"
?
Thanks,
-Chris W.
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Monday, January 05, 2009 11:33 AM
To: users@cxf.apache.org
Cc: Wolf, Chris (IT)
Subject: Re: CXF query U
I know there are several special query strings for WSDL and JavaScript,
i.e. :
http://host/service?wsdl
http://host/service?js
...but I thought there was also one for getting the schema part of the
WSDL, i.e. something like http://host/service?xsd (that doesn't work)
Is this true? What are all
Currently, we have some code that defines a custom fault in the
WSDL. Each service operation in the service impl is bracketed
by try/catch which wraps whatever is caught in the custom
fault and rethrows that.
I'm thinking our lower layers should always throw unchecked
exceptions and the service
I'll file when I verify for sure with a programmatic client.
Thanks...
-Chris W.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 26, 2008 3:18 PM
To: users@cxf.apache.org
Cc: Wolf, Chris (IT)
Subject: Re: Dealing with non-UTF-8 messages
OTECTED]
Sent: Wednesday, August 20, 2008 11:23 AM
To: users@cxf.apache.org
Cc: Wolf, Chris (IT)
Subject: Re: Dealing with non-UTF-8 messages
Chris,
On Wednesday 20 August 2008 4:50:52 am Wolf, Chris (IT) wrote:
> From looking at the SOAP spec, it seems that it's the responsibilty of
&g
s had prologs with
encodings, all would work.
Better, put an interceptor at the front to transcode to UTF-8 or add
prologs?
Can you tell us if this problem is specific to some app of yours or more
generic, to help motivate (or not) effort?
On Tue, Aug 19, 2008 at 4:47 PM, Wolf, Chris (IT)
<[EM
logs?
Can you tell us if this problem is specific to some app of yours or more
generic, to help motivate (or not) effort?
On Tue, Aug 19, 2008 at 4:47 PM, Wolf, Chris (IT)
<[EMAIL PROTECTED]> wrote:
> We now have some messages that contain iso-8859-1 (but non-ascii)
> characters, whic
We now have some messages that contain iso-8859-1 (but non-ascii)
characters,
which apparently, are not UTF-8, e.g. accented characters used in
Spanish and/or
French. These are causing exceptions citing invalid UTF-8 character
sequences.
I was able to eliminte one source by explicitly setting the
Thanks Dan and Benson.
-Chris W.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 12, 2008 2:11 PM
To: users@cxf.apache.org
Cc: Wolf, Chris (IT)
Subject: Re: Service-enable legacy code via ServerFactoryBean and
CXFServlet
With spring config, yes
Great, thanks I'll see how it goes...
-Chris W.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 12, 2008 2:09 PM
To: users@cxf.apache.org
Cc: Wolf, Chris (IT)
Subject: Re: ArrayIndexOutOfRange exception problem in
URIMappingInterceptor
We have a use-case of needing to service-enable some legacy code, which
we can't modify. As a POC we were able to service-enable it using
ServerFactoryBean (and presumably, ReflectionServiceFactoryBean). This
works
fine in the standalonoe endpoint model of deployment, but now we want to
deploy
SOAP client might be a option you would
consider.
On Tue, Aug 12, 2008 at 11:20 AM, Wolf, Chris (IT) <
[EMAIL PROTECTED]> wrote:
> Benson,
>
> We can look at that, but more generally, I was hoping to see the
> URIMappingInterceptor ignore GET parameters that we
@cxf.apache.org
Subject: Re: ArrayIndexOutOfRange exception problem in
URIMappingInterceptor
How about using our JavaScript client generator to talk SOAP from the
browser?
On Fri, Aug 1, 2008 at 9:25 AM, Wolf, Chris (IT)
<[EMAIL PROTECTED]> wrote:
> We're not going to ditch SOAP
tially XML over HTTP so why not use their
common ground to your advantage.
The schema part of your WSDL will still be valid so your interface
"contract" is still there. Saves you have to do too much which ties your
code to a specific implementation too.
Brad.
On Fri, Aug 1, 2008 at 3:05
We want to deploy services that are consumable either via conventional
POST of a request document,
or via RESTful invocation. It seems that wrapped-doc/literal has the
feature of being able to do that
without resorting to any extra work via the URIMappingInterceptor, which
is wired in by default.
Jul 2, 2008, at 5:45 PM, Wolf, Chris (IT) wrote:
> Dan,
>
> I'm doing something similar to this, but in my case, the
> WebServiceContext is not being injected, even though this was working
> in a smaller-scale POC.
That's not good. Are you using spring proxies or a
Dan,
I'm doing something similar to this, but in my case, the
WebServiceContext
is not being injected, even though this was working in a smaller-scale
POC.
I'm using setter injection rather then field injection, but as
mentioned,
this worked in my POC. So in my impl I have:
@Resource
p
According to this posting:
http://weblogs.java.net/blog/kohsuke/archive/2006/12/jaxws_ri_now_se.htm
l
...the JAX-WS reference implementation (Metro, I guess) has a facility
to include server-side stack trace
along with the SOAP Fault message. (maybe in the FaultDetail section?)
Is there a way t
only work on JDK-1.6.0_04
> or above?
>
> thanks and regards,
> bharath
>
> "Wolf, Chris \(IT\)" <[EMAIL PROTECTED]> wrote on
> 06/24/2008
> 02:26:31 PM:
>
>
>> If you use JDK-1.6.0_04 or above, then the JAX-WS API is part of the
>> runti
If you use JDK-1.6.0_04 or above, then the JAX-WS API is part of the
runtime.
-Chris W.
-Original Message-
From: Bharath Thippireddy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2008 2:24 PM
To: users@cxf.apache.org
Subject: Missing jaxws-api-2.1-1.jar in CXF 2.1.1
We were tryi
QUEST);
Willem
Wolf, Chris (IT) wrote:
> ...on second thought, having the request headers is only part of what
> I need, so if anybody knows how I can access the HttpServletRequest
> object from an intercetor, that would be awesome...
>
> thanks,
>
> -Chris W.
>
> P.S.
message would be helpful,
I have not learned too much yet reading the source of existing
interceptors...
-Original Message-
From: Wolf, Chris (IT)
Sent: Monday, June 23, 2008 5:57 PM
To: users@cxf.apache.org
Subject: RE: How to access HTTP request/responce from interceptor?
I actually looked
:
headers.entrySet())
System.out.println(header.getKey() + " : " +
header.getValue().get(0));
Thanks,
-Chris W.
-Original Message-
From: Wolf, Chris (IT)
Sent: Monday, June 23, 2008 5:24 PM
To: users@cxf.apache.org
Subject: How to access HTTP request/responce from intercepto
I read the docs, and only found this:
http://cwiki.apache.org/CXF20DOC/servlet-transport.html#ServletTransport
-AccessingtheMessageContextand%2ForHTTPRequestandResponse
However, I would like to access the the HTTP request object from my
subclass of
AbstractPhaseInterceptor - how would I do tha
w, if you use Metro, they want you to put the 2.1 JAXB jars in the
> endorsed directory of the SDK because the default JAXB in the JRE is
> 2.0, and Metro can't work with those. It *may* be the same story with
> CXF, i.e., JAXB 2.1 is needed.
>
> HTH,
> Glen
>
>
>
Just switched up to CXF-2.1.1 from 2.0. I see that JAXB in now
available
in JDK-1.6.0_04, so I remove external JAXB jars, however, I then get
two problems:
1.) wsdl2java won't run. To fix this, I need to put back the external
JAXB jar, "jaxb-xjc.jar",
however, I can still leave out jaxb-api
d to Tomcat
On Jun 12, 2008, at 11:51 AM, Wolf, Chris (IT) wrote:
> Dan,
>
> I just ran a live StAX factory configuration test; my web app is
> configured as
> follows:
>
> javax.xml.stream.XMLEventFactory:
> com.sun.xml.stream.events.ZephyrEventFactory
> javax.xml.str
:
com.sun.xml.stream.ZephyrWriterFactory
This is identical to the previous April snapshot, which does not exhibit
the
wsdl output problem that I get with CXF-2.1 release.
Thanks,
-Chris
-Original Message-
From: Wolf, Chris (IT)
Sent: Thursday, June 12, 2008 10:15 AM
To: users
d in the latest 2.1.1 snapshots (to work with either
parser).For 2.1 release, you will probably need woodstox instead
of Sun's.
Dan
On Jun 10, 2008, at 6:37 PM, Wolf, Chris (IT) wrote:
> I am not getting this exception:
>
> javax.xml.stream.XMLStreamException: NamespaceURI can
k--so I would
concentrate on being able to view it from a browser first.
HTH,
Glen
Wolf, Chris (IT) wrote:
>
> I am not getting this exception:
>
> javax.xml.stream.XMLStreamException: NamespaceURI cannot be null
>
> If anyone can help, that would be great.
>
> I rec
I am not getting this exception:
javax.xml.stream.XMLStreamException: NamespaceURI cannot be null
If anyone can help, that would be great.
I recently upgraded from an April snapshot to CXF-2.1, and now I get a
stack trace whenever I
do an HTTP GET for the WSDL from my published endpoint:
.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2008 2:37 PM
To: users@cxf.apache.org
Subject: Re: Bug CXF-830 closed, but I still have it.
On Jun 9, 2008, at 2:11 PM, Wolf, Chris (IT) wrote:
> Ok, I was able to try the 2.1 release, I a
4JInInterceptor will automatically do that if needed.I'm not
sure if that would change anything (it shouldn't).
Dan
On Jun 6, 2008, at 5:03 PM, Wolf, Chris (IT) wrote:
> I am trying to configured the out-of-the-box CXF security
> interceptors, but I am getting a NullPointer
008, at 5:03 PM, Wolf, Chris (IT) wrote:
> I am trying to configured the out-of-the-box CXF security
> interceptors, but I am getting a NullPointerException:
>
> INFO: Interceptor has thrown exception, unwinding now
> java.lang.NullPointerException
> at
> org.apache.cxf
I am trying to configured the out-of-the-box CXF security interceptors,
but I am getting a NullPointerException:
INFO: Interceptor has thrown exception, unwinding now
java.lang.NullPointerException
at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:658)
at
org.apa
sorry.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 3:29 PM
To: users@cxf.apache.org
Subject: Re: Using AOP in CXF service impl
On Jun 5, 2008, at 2:51 PM, Wolf, Chris (IT) wrote:
> Dan,
>
> Thanks for the help. Yes, it wa
I recommend not touching the "schemaLocation" settings. You can
override this externally with an
XML catalog, which can redirect to a local copy. In Eclipse:
Window=>Preferences=>Web and XML=>XML Catalog, then press "Add".
Also see:
http://www.eclipse.org/webtools/community/tutorials/XMLCata
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 3:29 PM
To: users@cxf.apache.org
Subject: Re: Using AOP in CXF service impl
On Jun 5, 2008, at 2:51 PM, Wolf, Chris (IT) wrote:
> Dan,
>
> Thanks for the help. Yes, it was Spr
PI.
CXF doesn't use proxies on the server side. Spring must be doing
something there.
Dan
On May 23, 2008, at 1:52 PM, Wolf, Chris (IT) wrote:
> I tried using Spring's AOP support classes to implement service
> authorization code in my CXF service, for the reason of not
XF service impl
Wolf, Chris (IT) wrote:
> static class ServiceCallPointcut extends StaticMethodMatcherPointcut
{
> public boolean matches(Method m, Class targetClass) {
> return (targetClass == this.getClass() &&
> m.getName().matches(&
I tried using Spring's AOP support classes to implement service
authorization
code in my CXF service, for the reason of not cluttering up my service
code
with security code (and maybe will also add auditing/tracing). This
seems to be
to classic use-case for AOP.
Unfortunately, the AOP implem
Not sure about your JVM arg, but to get CXF working in WLS-9.2,
I had to make the following adjustments to weblogic-application.xml:
http://www.bea.com/ns/weblogic/90";>
org.apache.xerces.jaxp.SAXParserFactoryImpl
org.apache.xerces.jaxp.
45 matches
Mail list logo
