Hi Bjorn,
Well, we use the following snippet with spring and cxf 2.1:
Notice the absence of your service factory, in theory i believe this should
default but in our case
we had to add it.
Other then that I dont see much wrong with your code and spring context.
Regards,
L
Hello,
when using implementor attribute as spring bean (e.g. #beanId), or some
other stuff, then probably you have to use also implementorClass attribute
and as value a full class name of generated portType (using wsdl2java).
otherwise cxf doesn't know, what to do .. there are no attributes vis
Hi Bharath,
maybe you have to add some more attritbutes to endpoint .. for me it works
... i'm using all as you plus
serviceName (without this it'll be created as java first and soap action
will not be send .. and maybe also validation doesn't work ?) and
implementorClass (but i'm using aop p
We need to hook up a GWT app to our web services (SOAP). We don't want to use
GWT RPC. We are thinking about exposing our services as JSON...ie...instead of
SOAP in/out, we take JSON in/out, but "everything" else is pretty much
RPC...ie...not REST.
Can this be done with CXF? In many ways, DW
Hi Leo,
I am getting a similar error and I have been scouring the forums to find
someone with the same problem.
I grabbed the cxf v2.1 source and did a test with their spring hello world
example. I included all the included dependencies in my test project but
upgraded Spring to the latest v2.5.4
As of the current state of the trunk, I have fairly good reason to believe
that the new JaxWsDynamicClientFactory would create proxies that could talk
to your OpenOffice service.
I can't quite prove it. When I created a service inside CXF that used the
same style of stuff, the unusual (perhaps non
Yes,
I have created one https://issues.apache.org/jira/browse/CXF-1617
willem.jiang wrote:
>
> I think this could be a bug of CXF. Could you please fill a JIRA[1] for
> it?
>
> [1]http://issues.apache.org/jira/browse/CXF
>
> Willem
>
> gdprao wrote:
>> Finally I could able to find the sol
My apologies...not sure why YHOO EMAIL decided to send out half a dozen
messages...in the wrong encoding...I am now going with plain old text just to
be sure...
So my GetMsgReq class contains multiple properties like id, name, description,
etc...
How do I actually form the URL that I can simpl
YAHOO.Shortcuts.hasSensitiveText = false;
YAHOO.Shortcuts.sensitivityType = [];
YAHOO.Shortcuts.doUlt = false;
YAHOO.Shortcuts.location = "us";
YAHOO.Shortcuts.document_id = 0;
YAHOO.Shortcuts.document_type = "";
YAHOO.Shortcuts.document_title = "Real McCoy Re: REST Annotation in CXF 2.1";
YAHOO.
I think this could be a bug of CXF. Could you please fill a JIRA[1] for it?
[1]http://issues.apache.org/jira/browse/CXF
Willem
gdprao wrote:
Finally I could able to find the solution to this problem. The following
configuration and code snippets might be useful to others struggling with
the s
Finally I could able to find the solution to this problem. The following
configuration and code snippets might be useful to others struggling with
the same problem.
It looks like CXF had a bug in not sending username and
password values.
applicationContext.xml:
---
http
We are trying to validate the soap request/responses on the server side by
using the "schema-validation-enabled" ,but i do not see any validation
happening.Below is the end-point definition from our cxf-servlet.xml.Is
this a bug?
The "A class/interface with the same name
"com.sforce.soap.partner.DescribeLayout" is already in use" error is
from jaxb and, per spec, requires the user to remap any conflicting
classes via the customization things. HOWEVER, while debugging the
salesforce stuff, I added a flag to wsdl
Hi,
The sample in
\apache-cxf-2.1\samples\corba\hello_world
shows a RPC style webservice client that goes through to a corba server.
Is there a way to get a Document/literal output from the CXF/JAX-WS Client?
I'd like to XSLT the output from a corba server.
As I understand, the corba stubs are
I think I'm confused.
The purpose of the dynamic client is to allow a client to talk to a service
without carrying any compiled code for the client's data model. The more
complicated the service, the less unlikely this is to be useful. If the
dynamic client creates a set of complex bean classes, y
Sorry, I wasn't notified that you answered the mail list, and I was so busy I
forgot to have a look to it.
So, like I said, the modifications you made
(http://issues.apache.org/jira/browse/CXF-1600 actually !) work great ! I
had to regenerated the classes and edited my client code (not a big deal,
Ok, so what about using XmlBeans just for plain marshalling/unmarshalling
of XML in CXF? How can this be accomplished? A link to a sample would be
gladly appreciated
Thanks,
Juan
Daniel Kulp <[EMAIL PROTECTED]>
27-05-08 07:57 PM
Please respond to
users@cxf.apache.org
To
users@cxf.apache.o
OK, what about that tool then: org.apache.cxf.tools.java2ws.JavaToWS
The direct benefit of this is that you would be able to handle soap
encodings (major/critical) with the dynamic client and to have a
different service model (I guess) since you could set a different
databinding (minor).
In term
I've made more investigation as the test project I tried to package did not
reproduce the issue.
I found that removing asm 2.2.3 from the project classpath fixed my issue.
Is there something wrong with this version ?
2008/5/28 Daniel Kulp <[EMAIL PROTECTED]>:
>
> Any chance you can file a jira
That's very nearly what it does already.
wsdl2java only supports JAXB, because it uses JAXB xjc facilities to
generate code.
That's what the DynamicClientFactory does, too.
On Wed, May 28, 2008 at 9:22 AM, Benjamin Coiffe <[EMAIL PROTECTED]>
wrote:
> I am wondering if the DynamicClient could
I intentionally left this out of the CXF javascript client, since the means
for enabling cross-scripting is very browser-specific. So I endorse the
proxy trick.
On Wed, May 28, 2008 at 10:00 AM, Vassilis Virvilis <[EMAIL PROTECTED]>
wrote:
> Hi everybody,
>
> As everybody knows cross site scripti
Any chance you can file a jira with a small test case?
My major concern is "why is it getting into the wrapper helpers at
all"?According to the JAXWS spec, the elements in the wrapper type
must NOT be nillable. If there are nillable=true flag there, it
cannot be considered unwrappabl
Any chance you can file a JIRA and attach a small sample that shows
the issue? I modified one of the samples and it seems to work fine,
but your setup might be different than the simple things we use
there. I'd like to see the test case to see what may be causing it.
Dan
On May 28,
It works fine when setting it via java api, but i'd like to configure stuff in
the spring.
I use version 2.1.
Piotr
> Date: Wed, 28 May 2008 20:02:21 +0800
> From: [EMAIL PROTECTED]
> To: users@cxf.apache.org
> Subject: Re: Setting timeouts
>
> Which version of CXF are you using?
> Did you tr
My issue is related to the following declaration :
As you can notice, the schema set nillable="true" AND minOccurs="0"
This schema has not been writen by XSD experts, and from MSDN documentation
I can read that nillable implies the element is required.
Can you confirm this ?
I can't find th
Hi everybody,
As everybody knows cross site scripting calls (from javascript) are dissallowed
by the browser.
If you absolutely want to call a webservice in a machine different from your
web server you will need a php proxy that will reside into the same machine
with the javascript script and
I am trying to use the CXF JMS client to asynchronously invoke a SOAP/JMS
service. My efforts thus far have been unsuccessful. During my
troubleshooting, I located the following lines of code in
JMSConduit.JMSOutputStream.doClose():
commitOutputMessage();
if (!isOneWay) {
handleResponse();
}
What should I do to get xmlbeans databinding on the client side with CXV
2.1? I've used xmlbeans to generate Beans from schema. How do I cast
one of the responses to the generated xmlbeans?
Thanks in Advance
Thomas
On Tue, 2008-05-27 at 22:57 -0400, Daniel Kulp wrote:
> On May 27, 2008, at 1:27
I am wondering if the DynamicClient could not be re-implemented to
better re-use your tools and other features.
DynamicClientFactory.createClient could invoke wsdltojava, load the
ClientProxy using ClientProxyFactoryBean. Then, you return the Client
from the client proxy...The big deal is to find
Hey,
We just replaced our default streamparser with the woodstox parser, running
under glassfish. Problem
solved here, maybe it will for you too ?
Regards,
Leo
Van: Nikolaj A. [mailto:[EMAIL PROTECTED]
Verzonden: wo 28-5-2008 14:50
Aan: users@cxf.apache.org
Ond
Hi,
Sorry for the late answer.
I recently swithed from cxf 2.0.5 to 2.1 in order to fix the
schema-validation issue, but a have the same problem with both cxf versions.
Here is a list of the changed jars (from SVN):
CXF 2.05 deleted from repository
commons-logging-1.1.jar
cxf-2.0.5-incubator.ja
Which version of CXF are you using?
Did you try to use the Java API to set the receiveTimeout value?
Willem
Piotr Skawinski wrote:
Hi,
I followed the cwike site and uses below spring configuration and still get the
same timeout exception:
http://www.springframework.org/schema/beans";
xml
I don't think we can do this with the Dynamic client.
The dynamic client uses the JAXB compiler to create classes on the fly based
on your schema, and then the CXF JAXB data binding maps the data back and
forth.
We don't have any kind of code generator for Aegis. Are you really sure that
you have
Hi,
I would like to resurrect this thread once again!
I understand that CXF does not support RPC/encoded AND soap encodings
(not exactly the same thing, right...)
But I have a Document/Literal ws using soap encodings and in particular
the soap-enc:arrayType. I read somewhere that Aegis DataBinding
Hi,
I followed the cwike site and uses below spring configuration and still get the
same timeout exception:
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:jaxws="http://cxf.apache.org/jaxws";
xmlns:http-conf="http://cxf.apa
35 matches
Mail list logo
