Hi -
I have a @WebMethod with a signature like this LIstMyObj getSomthing
() I'm using Doc/Lit Soap Binding, and MyObj is not been added to my
WSDL, I found issue CXF-340 that says how to add extra classes to
your JAXB context and i did someting like this (see code below) But
it doesn't
svn up the latest and building using mvn -Dmaven.test.skip=true
install -Peverything to build it.
I'm getting the following (this just started with today's update )
Any clues what to do ?
[INFO] [dependency:unpack-dependencies {execution: unpack-sources}]
[INFO]
Dan, I'm seeing the exact same behavior (values null when received by
client) using the wsdl2java generated client and jax:ws endpoints.
-bh
On 7/27/07, Dan Diephouse [EMAIL PROTECTED] wrote:
Hi Holger,
I'm going to take a stab in the dark and say its because you're using the
Ah.
That's my fault.I'm creating javadoc for the bundle jar from the
source jars.If the source jars aren't there, that barfs. I should
put that into the deploy profile or something so the source jars would
be found.
I'll get that fixed.
Thanks!
Dan
On Friday 27 July 2007 11:52,
That's exactly the same issue I'm seeing. It's just for complex types...
Strings, Longs both return successfully. Sorry for the duplicate topic...
I'm pretty much standing still at this point.
On 7/27/07, Holger Stolzenberg [EMAIL PROTECTED] wrote:
I am not sure if this helps but:
How do
I got my dependency injection of my DAO to work only to get lots of errors
likes this when deploying to tomcat. This looks bad. Does cxf not work with
hibernate and spring-hibernate support?
org.hibernate.Interceptor is an interface, and JAXB can't handle interfaces.
Hi Willem,
Yes, here you have the client code:
public class IntTest extends AbstractSpringTest {
private JMSDummyService jmsDummyServiceClient;
public void testJmsDummyService() throws Exception {
String message = jmsDummyServiceClient.getJMSHelloWorld();
I am not sure if this helps but:
How do you get the object, are using a debugging breakpoint at the return
statement of the service method or at the object returned by your client?
I also have an WS returning a business object (gets loaded through Spring AOP
transaction demarcation and
Thanks Marty - any chance you could contribute this via JIRA? We (the CXF
devs) should look at integrating this into our distribution for a future
release.
http://issuse.apache.org/jira/browse/CXF
Thanks!
- Dan
On 7/25/07, Marty Saxton [EMAIL PROTECTED] wrote:
Hi all:
I don't know if
CXF:wsdl2java creates the client side version of this object... what am I
missing so that it'll unmarshalled correctly?
Me to.
There is another strange thing in this:
The service causing the problems returns the Subscription.class object. In it
all fields BUT ONE are set to null when returned from the client proxy!!! This
field is another complex domain object of mine that is also loaded via
hibernate spring
Hi jeff,
Could you file a JIRA issue for this? I think we (the CXF devs) need to do
some debugging within GlassFish.
http://issuses.apache.org/jira/browse/CXF
Thanks,
- Dan
On 7/25/07, Jeffrey Metcalf [EMAIL PROTECTED] wrote:
Hi All,
I have an update on this issue. Apparently the problem
Hi Jeremy,
Aegis is a different databinding toolkit that CXF can use. The default
toolkit that CXF uses is JAXB. You may want to look at these docs for more
info:
http://cwiki.apache.org/CXF20DOC/aegis-databinding.html
Cheers,
- Dan
On 7/27/07, Jeremy Isikoff [EMAIL PROTECTED] wrote:
I got
OK... Hmm. Can you send along a test case/wsdl? That should help us debug on
our end and see if we can reproduce it.
- Dan
On 7/27/07, Brad Harper [EMAIL PROTECTED] wrote:
Dan, I'm seeing the exact same behavior (values null when received by
client) using the wsdl2java generated client and
OK. Fix is committed.
Thanks!
Dan
On Friday 27 July 2007 12:06, Daniel Kulp wrote:
Ah.
That's my fault.I'm creating javadoc for the bundle jar from the
source jars.If the source jars aren't there, that barfs. I
should put that into the deploy profile or something so the source
Hmm
I'm not sure why that doesn't work. We have a system tests for this and
that seems to pass fine:
https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/jaxb/
Brad,
I'm pretty sure this is fixed in the latest SNAPSHOTS.
http://people.apache.org/repo/m2-snapshot-repository/org/apache/cxf/apache-cxf/2.1-incubator-SNAPSHOT/
Any chance you could give it a try?
The other thing that might work is to run java2wsdl with the -s dir
option (and -classdir
On Friday 27 July 2007 11:36, Brad Harper wrote:
CXF:wsdl2java creates the client side version of this object... what
am I missing so that it'll unmarshalled correctly?
This is probably also fixed in the latest SNAPSHOT (or by using the
wrappers objects).
--
J. Daniel Kulp
Principal Engineer
Nope.. Same error. Even tried adding the JaxWsServiceConfiguration along
with the AegisServiceConfiguration. I think I'll just have to study the
spring docs a little more.
On 7/27/07, Dan Diephouse [EMAIL PROTECTED] wrote:
Hi Dave,
The problem is when you supplied the aegis configuration you
The snapshot and adding @ResponseWrappers solved my service issues as long
as I use a client other than CXF. I've testing utilities I can use for
now. My main issue is when I enable my transaction advice. Simply enabling
this section in my config causes 4 of my 10 services to fail with the
I just though of something. I don't have aegis.xml config files for all
classes only some of them. Could this be the reason this is not working?
On 7/27/07, Dave Kallstrom [EMAIL PROTECTED] wrote:
Nope.. Same error. Even tried adding the JaxWsServiceConfiguration along
with the
Brad,
I'm 95% sure this is my fault again. :-(
The last snapshot is from the 25th and that did break the ListObject
stuff.I fixed it yesterday, but didn't deploy a new snapshot. I'm
doing that now, but that will take an hour or so.
Couple notes:
That use of the @ResponseWrapper is
Anybody successfully gotten spring cxf, spring and hibernate working? I can't
seem to get the aegis databinding to work. I tried configuring it like an
example i saw:
jaxws:endpoint
id=reportingService
implementor=#reportingServiceImpl
address=/ReportingService
I've gotten it working with JAXB but not aegis. I'll try to plugin the
aegis bean you specified and let you know what I find out.
On 7/27/07, Jeremy Isikoff [EMAIL PROTECTED] wrote:
Anybody successfully gotten spring cxf, spring and hibernate working? I
can't seem to get the aegis databinding
Hello All,
I have two CXF endpoints that implement the same interface. One
endpoint is a live endpoint and the other is a mock endpoint that
returns dummy data. They are configured to use different endpoint
addresses, and CXF serves them up at these different addresses, but...
the WSDL for my
Brad, I'd love to see your JAXB code and setup I had all kinds of errors using
that one because jaxb couldnt handle lots of internal interfaces in the
hibernate stuff. Maybe it shouldn't have been seeing these to begin with?
- Original Message
From: Brad Harper [EMAIL PROTECTED]
To:
Julio and Brad, thanks so much for your help. It works fine with jaxb once you
hide the DAO injection setter methods in the implementation class.
- Original Message
From: Jeremy Isikoff [EMAIL PROTECTED]
To: cxf-user@incubator.apache.org
Sent: Friday, July 27, 2007 7:49:33 PM
Subject:
Hi Christopher -
Are you specifying your service name and port on your @WebService
annotation?
On Jul 27, 2007, at 4:52 PM, Christopher Moesel wrote:
bean id=liveDAO class=com.myco.LiveDAO /
bean id=liveWebService class=com.myco.WebServiceImpl
property name=dao ref=liveDAO /
/bean
Michal,
Right now, we don't support any Provider (or Dispatch) that takes the raw
CXF Message types. That's a good suggestion though. Could you log a
Jira for it?
What's worse, looking at the code for the Dispatch/Provider stuff on
trunk, it only will work for XML and SOAP bindings. It
29 matches
Mail list logo
