Hi Benson,
I am confused about the Webapp#2's log.
[java] Apr 9, 2008 9:11:35 PM
org.apache.cxf.transport.local.LocalTransportFactory createDestination
[java] INFO: Creating destination for address
local://RosetteTextAnalyzer
It looks you create the same local transport destination in
Hi All,
I'm having an issue calling a webservice on MS IIS from JBoss 4.2.2 with
Apache CXF 2.0.4 client deployed in a Spring application.
The deployed service doesn't seem to support client calls from JBoss with
Transfer-encoding chunked in the request header. Sometimes the service
system
I see your point. Maybe I made a cut-and-paste error and set up the service
factory instead of the proxy factory.
On Thu, Apr 10, 2008 at 4:14 AM, Willem Jiang [EMAIL PROTECTED]
wrote:
Hi Benson,
I am confused about the Webapp#2's log.
[java] Apr 9, 2008 9:11:35 PM
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]
OK, using wildcard *.http-conduit as the conduit name did the trick.
I still don't see why the specified name doesn't work though...
gbuys wrote:
Hi All,
I'm having an issue calling a webservice on MS IIS from JBoss 4.2.2 with
Apache CXF 2.0.4 client deployed in a Spring
On Thursday 10 April 2008, Benson Margulies wrote:
Willem,
The log messages from RSFB are a bit confusing. Notice that the first
set ends with a publish address and the second with a destination
address.
I'll go read the code, but now that I'm awake I can't imagine how the
local transport
My SOAP message has an object Foo, which has a body type as anyType. I am
using JAXB to generate that anyType body.
Now when i look at the Message that is being generated, there is one extra
tag as :
ns4:Body xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:ns6=http://my.a.b.c.com/v1;
I noticed on the CXF Roadmap
(http://cwiki.apache.org/confluence/display/CXF/Roadmap) page it references
JiBX and the possiblility that it may be in version 2.1 or may slip to
version 2.2. I was curious if anyone could tell me if it has been included
with 2.1 or not? If it has is there any
I'm using CXF 2.0.5. My Web Service is as follows:
@WebService(endpointInterface = com.sybase.it.quoting.QuoteBroker,
portName = QuoteBroker, targetNamespace =
http://quoting.it.sybase.com;, name = QuoteBroker)
@SOAPBinding(parameterStyle = ParameterStyle.WRAPPED, style =
Style.DOCUMENT, use =
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
Glen,
Thanks ever so much! This is exactly what I needed to further my
understanding.
You Da Man!!!
Chris Mathrusse
[EMAIL PROTECTED]
Sybase, Inc
One Sybase Drive
Dublin, CA 94568
(925) 236-5553
Glen Mazza [EMAIL PROTECTED]
04/10/2008 06:13 PM
Please respond to
Hi,
I'm writing some code that will allow me to deploy webservices that has been
setup as ServicePoints in Hivemind. This way I can build components (JARs)
with the webservice that I want to deploy and just add them to the classpath
of my WAR project and they will deployed. No need to configure
14 matches
Mail list logo
