Chad, I would go ahead and update OC4J with the Xerces parser--that is a
very common procedure for that app server, indeed so common that the
process for it is defined within the OC4J manuals. More information on
this and a few other tricks I have found with OC4J are here:
You're placing those attributes in the SEI (service endpoint interface, which
is autogenerated by wsdl2java), which is incorrect--they are supposed to go
with the SEI *implementation* (the class that implements it).
See sample here: http://www.jroller.com/gmazza/date/20080417#WFstep6
Not directly, but with Linux there's the wget command that returns the
result from an HTML page (or a WSDL...), which you perhaps can pipe into a
file which you can then use as an argument to wsdl2java.
There's also an issue of dynamic clients, which I don't know much about but
may be what
Another option is asynchronous client calls, first paragraph of here:
http://www.jroller.com/gmazza/date/20080308
2008-04-22 Arul Dhesiaseelan wrote:
[EMAIL PROTECTED] wrote:
When debugging our services, sometimes the time spent debugging is greater
that the time-out period for the client
Steps #7 and #8 here (look at the web.xml and ws-beans.xml file):
http://www.jroller.com/gmazza/date/20080417#WFstep7
Also, you can configure multiple config files separated by commas,
similar to here to keep your web service stuff separate:
http://www.jroller.com/gmazza/date/20061128
HTH,
Glen
I don't know, but perhaps Steps 7 and 8 of my example
(http://www.jroller.com/gmazza/date/20080417) might give you a hint.
Glen
2008-04-21 stevewu wrote:
Hi all,
I am converting the ws-addressing sample in cxf 2.0.5 to a servlet version.
When I deploy and run, I am getting the following
Here's information on our logging options:
http://cwiki.apache.org/CXF20DOC/debugging.html
2008-04-21 (月) の 16:02 -0700 に greenstar さんは書きました:
It appears to print Exception.getMessage(). NullPointerException has no
message, which explains why it prints null in this case.
How can I
2008-04-20 (日) の 15:22 +0200 に Leos Literak さんは書きました:
Hi,
I want to add soap stack to my web application. I decided for CXF. This
page http://cwiki.apache.org/CXF20DOC/servlet-transport.html shows it
could be possible. I set up web.xml and now I want to bind the servlet
to bus, as
I've never used our wsdl2js functionality, but apparently there are four
js_ samples here[1] that might provides hints for you.
HTH,
Glen
[1]
http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/
2008-04-20 Tim Perrett wrote:
Hey chaps,
Just having a
I added it to our wiki articles page[1], it may take a couple of hours
to show up though--thanks!
Glen
[1] http://incubator.apache.org/cxf/resources-and-articles.html
http://wiki.netbeans.org/ApacheCXFonNetBeans
This may be useful for beginners.
Cheers,
Arul
Wow. This is neet. I didn't know about this one at all. I honestly
though JAXB wouldn't do it. I learned something today. :-)
Thanks Glen!
Dan
On Thursday 10 April 2008, Glen Mazza wrote:
Here you go:
https://jaxb.dev.java.net/guide
Perhaps my client example may help you:
http://www.jroller.com/gmazza/date/20070929
Glen
Am Freitag, den 11.04.2008, 18:21 +0100 schrieb Tim Perrett:
This interested me, as Im trying to get to grips with CXF.
I just tried to put together a basic client (and even tried the WSDL
below) but
I don't know what version of CXF you're using but 2.0.5 has some changes
that *might* reduce the number of com.ctc.wstx.exc.WstxEOFExceptions you
will be getting, and hopefully provide you a more useful error message:
http://www.jroller.com/gmazza/date/20080327
HTH,
Glen
Am Freitag, den
If you have followed the instructions in the paragraph starting with
The first thing to notice is... on [1] closely in order to come up
with the exact name, and it still doesn't work, then possibly we have a
CXF bug. It can be tricky to get right.
Glen
[1]
You seem to have done what I did[1, Step #8], but it is apparently not
working for you. Perhaps the name field of the http-conf:conduit is
incorrect and hence CXF is not picking up the command. Using
name=*.http-conduit as shown near the top here[2] might fix your
problem.
HTH,
Glen
[1]
Here you go:
https://jaxb.dev.java.net/guide/Mapping_cyclic_references_to_XML.html
Glen
Am Donnerstag, den 10.04.2008, 16:12 -0700 schrieb
[EMAIL PROTECTED]:
I'm using CXF 2.0.5. My Web Service is as follows:
@WebService(endpointInterface = com.sybase.it.quoting.QuoteBroker,
portName =
I wouldn't say it looks very good for JiBX support--I have not heard
much demand for it lately on this list. Axis2 has it I believe, and
Spring Web Services may be another option for you.
Glen
Am Donnerstag, den 10.04.2008, 14:46 -0700 schrieb ron_honeyman:
I noticed on the CXF Roadmap
Am Donnerstag, den 10.04.2008, 23:08 +0200 schrieb
[EMAIL PROTECTED]:
It works just fine until I realize that I want to import XSD schemas
in my
WSDLs to allow validation of the SOAP requests.
Now, I have several webservices sharing XSDs (one entity model for
several
services and so on) so
Server faults go into separate interceptor chains (second paragraph of
[1])--I have not done this before, but you should be able to reuse the
interceptors you have on your normal non-error chains for the error
situations.
HTH,
Glen
[1] http://cwiki.apache.org/CXF20DOC/interceptors.html
Am
Am Mittwoch, den 09.04.2008, 10:21 +0100 schrieb Tim Perrett:
Hey Daniel,
Thanks for your interesting reply.
Thus, to get it working for CXF, you would need to modify the schema
to
put the proper s:import in place to import the schema schema, then
include the binding file to
What happens if you place those JARs within your WAR (WEB-INF/lib
directory)? Perhaps there is a precedence issue that is resulting in
the older SAAJ jar still be picked up--placing it in the WAR might fix
the issue.
Also, googling CXF SAAJ Websphere (without quotes) returns 366
hits--could any
almost every time or every other time a new request comes in.
When I traced into CXF source code, I see the init and destroy method of
CXFServlet gets called all the time.
Do you know anything that will cause WebLogic to unload our web app?
Thanks
Tong
Glen Mazza-2 wrote:
I have
I have not worked with this type of problem before. Possible guesses:
1.) Anything in our WebLogic docs[1] that may be relevant for your
problem?
2.) We have two types of configuration for web services--via a
cxf-servlet.xml file and directly through Spring configuration[2]. If
you try the
I only know the wsdl2java way of doing this, and Luba in past has not
desired to go this route. As I've said earlier, I don't think SSL with
the simple front end is a robust design that should be taught to
users.
[1] shows how to create a wsdl2java-based web service client with a
cxf.xml file
I'm confused--intercept faults from outbound requests to a third web
service when the third service is not available If the third web
service was not available, how could it be returning faults to your
other two web services' requests?
Glen
Am Donnerstag, den 03.04.2008, 16:10 -0700 schrieb Web
Here's another example: http://www.jroller.com/gmazza/date/20071102
Am Freitag, den 04.04.2008, 07:58 +0800 schrieb Freeman Fang:
Hi Vijay,
We have mtom demo in the kit, which shows how SOAP message
with an attachment and XML-binary Optimized Packaging(mtom) work.
Regards
Freeman
This might help:
http://www.nabble.com/CXFNonSpringServlet-How-To--td15356670.html
Am Donnerstag, den 03.04.2008, 17:42 -0400 schrieb Daniel Kulp:
CXF can be used without spring for some very basic use cases.
Basically, simple JAXWS+JAXB client/server with no configuration (or use
API's
That sounds like a hint, Guillaume... ;-)
Am Donnerstag, den 03.04.2008, 12:04 + schrieb
[EMAIL PROTECTED]:
Will Spring-DM also be a part of this example?
Original Message
Subject: Re: Using CXF in OSGi (03-Apr-2008 13:48)
From:Guillaume Nodet [EMAIL PROTECTED]
Hmmm, because they very heavily interact with and emphasize interoperability
with Microsoft[1], you may wish to take a good look at GlassFish Metro
first. While I doubt Metro can handle everything you want below, it will
probably get you closest to where you want to be.
Glen
[1]
to implement our standard practice given the current behavior
of CXF.
Brent
Glen Mazza-2 wrote:
Note #4 of here[1] shows how the WSDL URL is created when you deploy
to an application server; as you can see, what you have in the wsdl
file is pretty much ignored web
I don't know if that is supported (or even if it should be for that
matter). Being informally defined, the simple front end is not very
secure, and wanting to use HTTPS on top of it is somewhat of a
contradiction. So if you want to use HTTPS, I think you should learn
the JAXWS front end. Like
Brendan,
What happens if you use SSL instead of TLS? AFAIK they are
synonyms.
Regards,
Glen
Am Dienstag, den 01.04.2008, 13:27 +0200 schrieb Brendan Maguire
(brmaguir):
Thanks for the reply Daniel.
I tried using the 2.0.5 libraries but am still getting the exact same
errors.
Am I
I believe you'd get the very same result with Metro (try it [1])--CXF is
performing according to spec. If you're unhappy with JAX-WS' design on
this issue, sending comments to the JSR[2] over the matter would
probably be the best solution.
Regards,
Glen
[1]
Resending...
Am Sonntag, den 30.03.2008, 20:24 -0400 schrieb Glen Mazza:
I have not done that before, but I think that process is configured from
the servlet/JEE container's end. (CXF does not authenticate the client,
the application server does.) Reading the documentation for your
servlet
This may be the problem: Try -Dcxf.config.file instead of
-Dcxf.config.file.url, perhaps.
Am Donnerstag, den 27.03.2008, 10:00 +0100 schrieb
[EMAIL PROTECTED]:
First of all thank you boys!
I really appreciate your valuable help.
How did you feed the CXF configuration to the server?
I
Providing you have the WSDL, you should be able to run wsdl2java and
have a ProcessingFailureException class that will contain that
information. Look at [1], in particular Step #4 - the wsdl:message
CorrelationIdNotFoundFault, Step #6, getAdditionResults() method to
see how this object gets
Just a guess, but that sounds something like a denial-of-service
attack--you may be overquerying the web service, and it is running out
of threads as a result.
Querying the WSDL just to see if the web service is working would seem
to be inaccurate. I can imagine the former working but the latter
1. That seems strange. Unless I'm not understanding you correctly, I would
think you just want to create one WSDL with 68 services (wsdl:operations),
and then proceed as follows: http://www.jroller.com/gmazza/date/20071019
2. It depends on your servlet container, not the web service stack.
Yes, look at catch (CorrelationIdNotFoundFault e) {...} in Step #10 of
[1] below.
HTH,
Glen
[1] http://www.jroller.com/gmazza/date/20080308
Am Montag, den 24.03.2008, 08:34 -0700 schrieb Mehmet Imga:
Hello,
is there a way to throw nested exceptions in webservices?
for example I would
23.03.2008, 14:39 -0700 schrieb Kalle Korhonen:
On Sat, Mar 22, 2008 at 10:47 PM, Glen Mazza [EMAIL PROTECTED] wrote:
I'm not sure, but I think you're trying to create a dynamic client which
is unfortunately not working for you. Hopefully someone else can answer
your specific question
I'm not sure, but I think you're trying to create a dynamic client which
is unfortunately not working for you. Hopefully someone else can answer
your specific question on this, but in the meantime, you might wish to
try the more traditional route of getting the WSDL and XSD's on your
machine
Am Freitag, den 21.03.2008, 01:27 -0400 schrieb Wolf, Chris (IT):
If I run my service inside a Tomcat-5.5 runtime configured in
Eclipse-3.2, all works fine.
I run the very same code, deployed on Tomcat-5.5 on Linux, I get this
error.
If anyone can suggest something short of debuggin the
the
Authorization header may contain just an encoded username in certain
circumstances.
-Chris
-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 7:12 AM
To: cxf-user@incubator.apache.org
Subject: Re: Error
That web service is old-fashioned rpc/encoded. CXF and Metro use the
incompatible doc/lit or rpc/lit--our wsdl2java can't work with it. Axis 1
(not Axis 2) may help you.
(Although I think there was an effort in the past for CXF to handle
rpc/encoded--I don't know what if anything became of
, disclosure or distribution is prohibited. If you are not
the intended recipient, please contact the sender and destroy all copies
of the original message.
-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2008 7:02 PM
To: cxf-user
Because they work heavily with Microsoft concering interoperability,
Metro is generally better documented[1][2] for accessing .NET services.
If you cannot get CXF working, you may want to try a Metro client.
Outside of authorization, the two stacks are rather easily swappable.[3]
Glen
[1]
I think you're using Maven. Trying using the goal of mvn
generate-sources instead, to see if that works. ([1], Maven Notes #2
at the very bottom.)
HTH,
Glen
[1] http://www.jroller.com/gmazza/date/20070929
Am Montag, den 10.03.2008, 11:01 -0700 schrieb mattrpav:
cxf-2.0.4-incubator, running
Check your serviceName value for the @javax.jws.WebService annotation
preceding your web service's implementation class, like here:
http://www.jroller.com/gmazza/date/20080308#MTstep6
HTH,
Glen
Am Sonntag, den 09.03.2008, 11:04 -0400 schrieb Wolf, Chris (IT):
Before posting this, I looked at
What are you putting in the WAR file--the web service or the SOAP
client?
Also, I'm unsure if you should be relying on the autogenerated
client--that is primarily a helper file not really part of JAX-WS
(GlassFish Metro I don't think provides it.) I've never bothered using
it.
The first thing
dkulp wrote:
In general, the jaxws way of doing this is to map the runtime
exceptions to a very generic soap fault that is fault code SERVER and
just the message (ex.getMessage()) is set into the fault message.
On the client side, this ends up throwing the generic SOAPFaultException
Hello, I have a general question for WSDL design regarding internal web
service errors not the fault of the SOAP client request, such as
database unavailable or system down or whatever.
For example, let's say I have a simple GetCapital web service that
takes a country and returns the name of its
My version works: http://www.jroller.com/gmazza/date/20071019
Perhaps you can see a delta between what you are doing and what I am doing
that will help you spot the error.
Glen
junker66 wrote:
I'm getting the following error while deploying a service in tomcat:
Mar 6, 2008 3:09:50 PM
Sadly, I was able to get this portion of your code below to work for
Metro but not CXF:
rc.put(BindingProvider.USERNAME_PROPERTY, userName);
rc.put(BindingProvider.PASSWORD_PROPERTY, password);
I have been meaning to look at this to find out the reason why. But in
the meantime,
We have our own java2wsdl tool you can use. Axis2's work I believe is
not JAX-WS standard, they do their own thing.
Glen
Am Dienstag, den 04.03.2008, 16:39 + schrieb John-M Baker:
Hello,
I appreciate I'm asking a lot of questions today - sorry. I guess I'm
adding lots to the mail
? For
this
particular instance, I'm doing a simple query that takes an enum object,
but
CXF doesn't seem to know how to convert the string to an enum (it throws a
class cast exception) unless I use POST.
Thanks,
Scott
On Mon, Mar 3, 2008 at 11:25 PM, Glen Mazza [EMAIL PROTECTED]
wrote
That's not WS-I Basic Profile compliant, because for many web service
stacks, it is the parameters that are used to determine which operation
is called.If you run wsdl2java with the validation option you should
see a warning to that effect. Metro also would complain about that,
although they
Can you mock out the web service calls to confirm that it is CXF eating
up your DBCP pool and nothing something else?
Glen
Am Montag, den 03.03.2008, 13:19 -0800 schrieb Michael McCaskill:
I'm coming from Spring-Webservices. I like that CXF supports contract-last
since I'm in a prototype,
Steps 1 and 2 of here[1] are how I downloaded and compiled CXF. Perhaps that
might be of help.
Glen
[1] http://www.jroller.com/gmazza/date/20080225
dkulp wrote:
No idea.
Couple suggestions:
1) What version of maven are you using? You may need 2.0.7. Not really
sure.
2) Can
I'm unsure if you're trying to change the URL that a SOAP client is using, or
a the URLs being employed by the web service.
If the former, Step 7 of [1] might help you. You can use dependency
injection to feed a URL to your SOAP client, and use the Java code in Step
#7 to dynamically change the
Forwarding to cxf-user list (email accidentally just went to
Christopher)
Am Donnerstag, den 28.02.2008, 21:58 -0500 schrieb Glen Mazza:
Possibly, but I don't think you should do that in a CXF-specific manner
that you are envisioning. (I don't know of a CXF-specific manner
myself
I think the answer is no, neither CXF nor GlassFish Metro support
interfaces as parameters. It's either a JAX-WS or JAXB rule, I'm not
certain.
Glen
Am Dienstag, den 26.02.2008, 15:07 -0800 schrieb Ayush Gupta:
In my web service, there is a method which takes an interface as its
parameter,
Phil, I updated the docs for both java2wsdl and java2ws, so others won't
have the same confusion. Sorry this happened to you.
Glen
Am Dienstag, den 26.02.2008, 13:42 -0500 schrieb Daniel Kulp:
On Tuesday 26 February 2008, Phil Weighill-Smith wrote:
That's the sort of answer I was looking
about xmime:expectedContentType, AFAIK. Do you
have the @MTOM annotation in place to enable the threshold?
On Fri, Feb 22, 2008 at 8:01 PM, Glen Mazza [EMAIL PROTECTED] wrote:
Some possibilities:
1.) From Step #5 of [1], make sure you have xmime:expectedContentTypes
declared in your WSDL
Comments below...
Am Montag, den 18.02.2008, 11:57 +0100 schrieb pierre post:
Hi all,
I have a problem when calling an Apache CXF Web service (CXF version
is
2.0.4) running under Apache Tomcat 6 from a Delphi client program.
The
third parameter JobParamBean that I receive in my Web
Am Freitag, den 22.02.2008, 10:35 -0800 schrieb yulinxp:
It's easy to set up for local server http://localhost:8080/
But if I want to see soap message between client amazon service,
http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl?
How do I know which port the
Our client SSL documentation is here: http://tinyurl.com/ytc77j. Per
Oleson's blog article mentioned at the top of the page has a simple
working sample.
Glen
Am Freitag, den 22.02.2008, 13:25 -0800 schrieb yulinxp:
CXF Client doesn't work for this example. I end up with using wsimport.
Am Freitag, den 22.02.2008, 13:19 -0800 schrieb yulinxp:
Thanks. I was following your web-log
http://www.jroller.com/gmazza/entry/sun_s_wsmonitor_tool
I save the wsdl file, and change soap:address from
soap:address
location=http://soap.amazon.com/onca/soap?Service=AWSECommerceService/
to
Some possibilities:
1.) From Step #5 of [1], make sure you have xmime:expectedContentTypes
declared in your WSDL (you can see me using it under element
name=getWeatherForecastResponse at the top).
2.) From Step #6 of [1], make sure you use @BindingType annotation just
before your web service
That class is most probably an autogenerated JAX-WS artifact. If there
is a WSDL file in the sample, run wsdl2java[1] on it.
Glen
[1] http://cwiki.apache.org/CXF20DOC/wsdl-to-java.html
Am Dienstag, den 19.02.2008, 21:08 -0500 schrieb jw:
Hi
I'm new to CXF and attempting to build
Here's a WSDL-first example I created:
http://www.jroller.com/gmazza/date/20071019
For just a pure client, of an already existing web service:
http://www.jroller.com/gmazza/date/20070929
HTH,
Glen
Am Dienstag, den 19.02.2008, 16:24 -0800 schrieb Daniel Lipofsky:
I am trying to learn CXF, I
Hello,
Can I program an interceptor in a web service's incoming interceptor chain
to dynamically route to another interceptor other than the one predefined in
its chain (and ignore all subsequent interceptors in the predefined chain)?
In other words, for an interceptor chain A-B-C-D, can I add
Yes, but you will need to follow the WS-I Basic Profile more closely,
and of course test your services with .Net clients. It would also
depend on the nature and complexity of your web services.
Truth be told, I suspect GlassFish Metro i.e., Project Tango, would be a
safer bet if .NET clients
Using DataHandler/MTOM?
http://www.jroller.com/gmazza/date/20071102
Glen
Am Donnerstag, den 07.02.2008, 14:34 +0100 schrieb
[EMAIL PROTECTED]:
Hi,
I'm developing a simple webservice which can take any object as input that
implements java.io.serializable and can return any of those:
I believe that can be enforced in the web.xml file that you distribute
your WAR with. For example, (another web app unrelated to web
services), line 41-51 of web.xml: http://tinyurl.com/yp6faz
Glen
Am Dienstag, den 05.02.2008, 12:44 -0500 schrieb [EMAIL PROTECTED]:
I want to make sure any
PhaseInterceptorChain[1] has add methods (lines 155 and 169) with a
force parameter, that, if true, will apparently force the interceptor
to be added to the chain (lines 475-496), even if there is another
interceptor with the same name.
I guess if you subclass PIC and just override the add()
Hello,
I have a question about the org.apache.cxf.message.Message.getContent(?)
method within interceptors.
The CXF sample interceptor[1] on line 49 has this call to get the
content (payload) of the SOAP message:
OutputStream os = message.getContent(OutputStream.class);
Question: Besides
Hello All,
As a result of upgrading from CXF 2.0.2 to 2.0.3, a test is failing because
the below class could not be found.
I'm using Maven for builds and tests, and am *not* bringing in every
possible CXF dependency as defined here[1].
java.lang.NoClassDefFoundError:
/apache/ws/commons/schema/extensions/ExtensionDeserializer
Glen
Glen Mazza wrote:
Hello All,
As a result of upgrading from CXF 2.0.2 to 2.0.3, a test is failing
because the below class could not be found.
I'm using Maven for builds and tests, and am *not* bringing in every
possible CXF
Am Freitag, den 18.01.2008, 10:49 -0500 schrieb Yadav, Yogendra (IT):
Hi,
I have already used wsdl2java -client to generate client code to
access a CXF service. The WSDL that I provided does include service
endpoint information. I see that, now at runtime the client code tries
to retrieve
Hello,
I'm having difficulty upgrading from CXF 2.0.2 to CXF 2.0.3 using Mavenized
builds. With CXF 2.0.3 (not 2.0.2), Maven keeps trying to download
nonexistent versions of jars (in particular, Version 1.0 of cxf-api and
cxf-rt-core, neither of which have 1.0 versions anywhere) and fails
No, Windows XP Professional, SP2.
dkulp wrote:
Geln,
You aren't, by any chance, on a Mac? Are you?
Dan
On Thursday 17 January 2008, Glen Mazza wrote:
Hello,
I'm having difficulty upgrading from CXF 2.0.2 to CXF 2.0.3 using
Mavenized builds. With CXF 2.0.3 (not 2.0.2
Thanks for the help Dan. I think I'm getting a solution--I just need to
explicitly state the version of cxf-api and cxf-runtime-core that I need in
the DependencyManagement/ section, rather than rely on Maven's default
dependency resolution. Another option that seems to work is using
dependency
Hello, at work I'm having slight difficulties in upgrading from CXF 2.0.2 to
2.0.3. I'm noticing a strange CXF dependency in one of our pom.xml files:
dependency
groupIdorg.apache.cxf/groupId
Hello,
This question is hard for me to phrase exactly, but for a SOAP request which
contains an input parameter which is resolved as a DataHandler by JAX-WS, is
there a way to determine the total size in bytes of that DataHandler object?
Can I rely on any HTTP headers for that information?
I'm
Am Donnerstag, den 10.01.2008, 05:14 -0800 schrieb Landslide:
Glen,
I understand that I am facing a challenging problem of class loaders and
class loading sequence, specifically for JBoss. As you can see, my CXF WAR
has everything it needs to run as I have included ALL jars from CXF lib
Note #4 here may also help clarify things for you:
http://www.jroller.com/gmazza/date/200710#notes
HTH,
Glen
Am Donnerstag, den 10.01.2008, 23:29 + schrieb Ian Roberts:
Pawel Janusz wrote:
I want to use this one but not working :(
jaxws:endpoint id=MyServiceService
There are periodically headaches involved in getting CXF to work with
JBoss, primarily classpath issues I believe. Perhaps searching our
archives[1] can be of help for you.
Glen
[1]
http://www.nabble.com/forum/Search.jtp?forum=16914local=yquery=jboss
Am Mittwoch, den 09.01.2008, 10:50 -0500
have been deleted at the
same time for completeness. So the fact that it still exists is a simple
over-sight.
Cheers,
Eoghan
Glen Mazza wrote:
Resending...
Am Montag, den 07.01.2008, 11:37 -0800 schrieb YI (William) ZHU:
Hi there,
I'm studying the sample ws_addressing
http://markmail.org/message/b7w4vugla43nmj7p?
Am Dienstag, den 08.01.2008, 12:43 -0800 schrieb yulinxp:
For my client, I look into the src to find out the setting for SOAP1.2. I
don't know whether there's a better way.
bean id=client class=demo.spring.HelloWorld
Resending...
Am Montag, den 07.01.2008, 11:37 -0800 schrieb YI (William) ZHU:
Hi there,
I'm studying the sample ws_addressing of CXF2.0.2.
I have two questions about the configure file handler_chain.xml:
1) where is the Java file for demo.ws_addressing.common.HeaderSnooper
class?
I
There are rather convoluted rules in the JAX-WS specification of when
bare vs. wrapped mode is used (and one of the committers recently found
a difference between the spec and both our and Metro's implementation.)
Still, working with Objects is still quite doable; see here [1], Step #7
for sample
Am Freitag, den 04.01.2008, 18:19 -0800 schrieb Kyle Sampson:
I'm currently using CXF 2.0.3. While playing around with WS-Addressing, I've
noticed a number of errors that occur when sending lots of messages.
Here, lots of messages = messages being sent in a while(true) loop
I've
been
Hello,
The handlerChain annotation[1] on an SEI implementation class has a
file member-value that indicates the location of the JAX-WS handler
configuration file (here[2] for example) relative to the SEI
implementation containing this annotation.
I'm not certain if this relative location refers
only be placed within the same
directory as the bytecode for the SEI implementation class. It cannot
read the file as a normal resource in WEB-INF/classes. I think this is
a bug--I'll submit a JIRA for it.
Thanks,
Glen
Am Samstag, den 05.01.2008, 09:33 -0500 schrieb Glen Mazza:
Hello
in the same package as the service class file.
Am Samstag, den 05.01.2008, 12:24 -0500 schrieb Glen Mazza:
OK, through trial and error I was able to answer my own question.
GlassFish Metro: The JAX-WS handler chain configuration file can either
be placed in the same folder as the bytecode
Am Freitag, den 04.01.2008, 06:04 -0800 schrieb Pierre Buyle:
Hi,
In Java, I have several different services interfaces using the same data
classes with JAXB annotations. Using CXF (2.0.3) and Spring, implementations
of theses interfaces are exposed as Web Services.
It works well with
Hello, I am trying to understand any architectural correspondances between
JAX-WS Handlers[1] and CXF interceptors. I can see from the interceptor
page[2] that a JAX-WS SOAP protocol handler more or less maps to a CXF
AbstractSoapInterceptor. I was wondering if there is an counterpart to the
I don't think you usually throw (or can even throw) RemoteExceptions
with JAX-WS. IIRC RemoteExceptions are for JAX-RPC only[1].
Glen
[1]
http://www.ibm.com/developerworks/webservices/library/ws-tip-jaxwsrpc3/
Am Donnerstag, den 03.01.2008, 12:53 -0800 schrieb yulinxp:
sample wsdl_first demos
Just a gamble here, but docs for the Mule-CXF transport seem to suggest
that CXF is picky on the SAAJ version it wants ([1], see With Mule
Standalone section.) You may need to override the SAAJ version that
WebLogic is using. How you do that is unfortunately quite JEE
server-dependent. You may
cxf.xml is for bus (generic service/client endpoing) configuration--I
don't know what you're trying to do to be able to answer your question
directly.
The Service configuration files section of [1] gives you two separate
ways of configuring a CXF-based web service. Also, Willem recently
created
1 - 100 of 227 matches
Mail list logo
