to use the data from the CORBA stream reader, but that doesn't even work
right now. Even trying a Source doesn't work.I think some Jira's
need to be added for that as well.
https://issues.apache.org/jira/browse/CXF-858
logged and tracked here [1]
Cheers,
Bo
[1] https://issues.apache.org/jira/browse/CXF-857
Dan Diephouse wrote:
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
not sure if this is relevant to my generics problem but I always get this
warning as well when deploying
INFO: Could not find the configuration file cxf.xml on the classpath
- Original Message
From: Jeremy Isikoff <[EMAIL PROTECTED]>
To: cxf-user@incubator.apache.org
Sent: Sunday, July
No, that wouldn't cause the problem.
The JaxWsServiceConfiguration isn't enough. We still need the
defaultServiceConfiguration in there. Can you try something like:
(if for some reason that doesn't work, try inversing the order, but I'm
pretty sure thats the right order)
Cheers,
- Dan
On
I managed to build the snapshot by commenting out the javadoc section in the
pom file. I now get this error on deploying to tomcat:
WARN DefaultNamespaceHandlerResolver:133 - Ignoring namespace handler
[org.apache.cxf.bus.spring.NamespaceHandler]: problem with handler class file
or dependent c
Just realized that we do support something similar:
public class MyService {
public void invoke(Exchange ex) {
Message in = ex.getInMessage();
Message out = ex.getOutMessage(); // not sure if the outmessage has been
created at this point or not, so you may have to experiment
...
}
}
On Sunday 29 July 2007 01:29, Jeremy Isikoff wrote:
> I'm using the 2.0 release and JAXB. I'd try the 2.1 if that fixes it
> but im not good enough at this stuff to figure out how to do a build
> from the source yet. When is that expected to be released as a jar?
We're hoping to start the release
