These might be enough:
javax.annotation
javax.jws
javax.jws.soap
javax.wsdl
javax.wsdl.extensions
javax.wsdl.extensions.http
javax.wsdl.extensions.mime
javax.wsdl.extensions.schema
javax.wsdl.extensions.soap
javax.wsdl.extensions.soap12
javax.wsdl.factory
javax.wsdl.xml
javax.xml.bind
javax.xml.bi
if your cxf libs and service sei/impl are in separate bundles then you
need to import some non-cxf namespaces also in your service sei/impl
bundles. just check the imports used by your sei, those should be
imported by your manifest...
for e.x. you would need javax.jws, javax.jms, javax.xml.ws, etc
we're using cxf inside osgi bundles... we just put all the libs in one
bundle and export required packages from there...
just had to be careful to import the javax.jws and some related
namespaces in other bundles where services are written since these
packages are available without import too but
I have a cxf webservice and a client generated using wsdl2java. When the
client tries to contact the service the parameters are being null. I am
unable to figure out the reason.Tried including all the jars from cxf.
Any answers are appreciated.
Thanks
--
View this message in context:
http://ww
I created a CXF OSGi bundle using the Eclipse Plug-in form Existing JAR
archive wizard.
I used the latest SNAPSHOT CXF JAR: cxf-2.1-incubator-SNAPSHOT.jar
I then added the org.apache.cxf package to the import-packages of my
manifest.mf
When I try to call my web services from my RCP application I
To whom it may concern,
I would also like to try out CXF OSGi bundles. I would love to use CXF in
my Eclipse RCP application I am writing. You mention there is a small
(untested) maven project to create the bundles. I would like to try it out
in my environment if possible. Where can I locate it
Thanks for your suggestions. I tracked down the problem and it turns out
that geronimo-ws-metadeta_2.0_spec-1.1.1.jar was being put on the WebLogic
classpath twice, which was causing the error.
Thanks again,
Ben
dkulp wrote:
>
>
> It may be the xml-apis.jar. I'm not sure why we have it
Hi
I'm not sure how many modules a CXF-specific HTTP_BINDING requires, but it
would be interesting to get a picture on how many modules a CXF JAX-RS frontend
needs.
The following dependencies are likely be needed only :
cxf-rt-core
cxf-api,
cxf-common-utilities
cxf-rt-transports-http
cxf-rt-tra
It may be the xml-apis.jar. I'm not sure why we have it in lib. It
shouldn't be needed. I'll try excluding it and seeing if things still
build.
Dan
On Thursday 07 February 2008, chengas123 wrote:
> Hi,
> I'm afraid I'm getting the QName issue again. I have no idea as to
> what was diffe
Hmm...
That should definitely work. I know it works for jaxws:endpoint defined
services as the TCK puts multiple endpoints in a war in several places
and I debugged some issues around it when they are in separate imported
files for 2.0.4.
Any chance you could send a war/project that dem
Rob,
The JAX-WS spec covers this fairly extensively. You might want to read
through section of 3.7 of the JAX-WS spec:
https://jax-ws.dev.java.net/spec-download.html
Basically, there are three ways to deal with "Service Specific
Exceptions" (as the spec calls them):
1) Very low level: throw
Let me start by saying that I am somewhat new to the CXF library and to JAXWS
in general. I would like to deploy the service under Tomcat 5.5. and I have
been able to get one of the samples to work using the standard CXFServlet
configuration. However, our application server environment does not i
Yea, definitely don't rely on it being a ByteArrayInputStream. The
DelegatingInputStream MIGHT be wrappering a ByteArrayInputStream, but if
the attachment is large and we had to stop streaming, it's most likely
been spooled to disk (so multi-megabyte attachments don't suck up all
the memory)
Eric,
I just noticed there is a 1.2 version (instead of 1.0-M1) at:
http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-javamail_1.4_spec/
Any chance you could give it a whirl? I'd be happy to update our deps
so future builds get that. Actually, I'll probably update all the
ger
Right now, a threadlocal would work.
That said, ideally you would use the exchange for storage (for cxf
interceptors) or the WebServiceContext for the jaxws stuff. That way,
if we change things in the future, it wouldn't break. We keep talking
about someday allowing the interceptor chain
Ronald Pieterse wrote:
and the file is uploaded. I though that if I just copy / paste and switch
server code to client code and vice versa the download part would work too.
It does indeed work until I try to do:
bis = (ByteArrayInputStream) file.getData().getContent();
At that line a Cl
I have a service with which I would like to upload and download files. The
uploading part goes great - I make the upload call like so:
UploadFileType uft = new UploadFileType();
uft.setFileName("somefilename.zip");
uft.setData(new DataHandler(new
FileDataSource("/var/tmp/s
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:
>
>
18 matches
Mail list logo