Thanks for your help. It is very helpful.
Boxiong
- Original Message
From: Benson Margulies <[EMAIL PROTECTED]>
To: users@cxf.apache.org
Sent: Monday, June 9, 2008 5:08:53 PM
Subject: Re: Does MTOM keep filename?
The MTOM spec specifies the use of a subset of MIME and a subset of XOP to
The MTOM spec specifies the use of a subset of MIME and a subset of XOP to
transmit an attachment. As Dan says, the spec probably doesn't prohibit
putting a file name into the MIME header, but it also doesn't define the
semantics of doing that. The spec just doesn't think about the idea of a
file n
Thank you for your answer. It is very helpful. But I kept wondering since email
keeps attachment file names but CXF MTOM does not, it is purely implementation
dependent and most Soap related toolkits choose not to do it due to the reason
you give. Is this right?
Boxiong
- Original Mes
So may be you can use ',' as a separator between multiple params in a single
path segment then ?
Cheers, Sergey
-Original Message-
From: Tim Morrow 2 [mailto:[EMAIL PROTECTED]
Sent: 09 June 2008 20:36
To: users@cxf.apache.org
Subject: RE: JAX-RS specifying multiple values in a pathparam
Solved, I think.
In the wsdl that references the schema we have a security import:
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
schemaLocation="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
/>
This itself incl
>From a protocol standpoint, the MTOM wire protocol does not carry a file
name. The fact that the data handler class carries a pathname is a bit of a
red herring. If you want to carry a file name, use another element.
It seems to me that there is some hypothetical possibility that the XOP/Mime
par
Hmm... possible.We have a copy of the xmldsig-core-schema.xsd in
the jar. Most likely that affects the SECOND case though, not the
first case.The internal catalog we use maps the full version into
the what's needed in the jar. Thus, the second one would probably be
using our i
Thanks very much!!
This blog posting opened my eyes to the mistakes we were making in our
attempt to generate client and service from the same WSDL.
I have things mostly working now -- the big breakthrough came when I fully
annotated our server Impl file so that the @WebService declaration inclu
I have a wsdl that refers to a external schema. The latter imports another
schema like this:
http://www.w3.org/2000/09/xmldsig#";
schemaLocation="xmldsig-core-schema.xsd"/>
This xmldsig-core-schema.xsd is located in the same folder that the wsdl and
the parent schema are located.
If I run m
Thanks.
I did also try that. request.getPathInfo() dropped _everything_ after the
first semi-colon in the path.
There seemed to have been a bit of a discussion regarding Tomcat's handling
of ";" in the path in 2006:
http://markmail.org/message/4h3kqe7cbwx3ujqi?q=marc+parameters+in+URL+path+seg
Yea, in general, the name is considered a system dependent property
and the client should get to chose what makes sense for them . If the
name is important, it should be transferred in the actual data.
I suppose we COULD throw the name into a mime header on the part, but
we'd be the only
Pardon the non-answer, but for my MTOM example
(http://www.jroller.com/gmazza/date/20071102), in step #11, I let the client
set the name. Wouldn't it seem more natural to let the client decide what
it wants the file it obtains to be called?
As an alternative, perhaps best to send a separate Stri
Hi
Perhaps you can do (note the trailing '/')
@Path("/{id1};{id2};{id3}/")
And then just do /1;2;3/ ?
Cheers, Sergey
-Original Message-
From: Tim Morrow 2 [mailto:[EMAIL PROTECTED]
Sent: 09 June 2008 17:51
To: users@cxf.apache.org
Subject: Re: JAX-RS specifying multiple values in a
Well, since we use wrapped doc-literal, our services are also able
to be invoked REST-style, so I use a JSP page with query strings
for quick and easy testing, hence the GET. Sorry about that.
I will look into using a real XML invoking method, perhaps
even an actual test client...
-Chris W.
I have a service that uses MTOM to send a image file. As a client I can get the
data, but the file name is lost. I have tried to set it in
ByteArrayDataSource.setName() and create a DataHandler using it on server side.
But still, the client always get null from DataSource.getName() and when I us
This looks like the incoming XML isn't valid. That's about the only
thing I can think of. Maybe do a wiretrace or something and see what
the XML looks like coming in?
Dan
On Jun 9, 2008, at 9:17 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]
> wrote:
Hi group,
After successfully test
On Jun 9, 2008, at 2:11 PM, Wolf, Chris (IT) wrote:
Ok, I was able to try the 2.1 release, I also commented out the
explicit
SAAJ interceptor from the config file, as you suggested. I am STILL
getting the NullPointerException. I notice that the WSS4J interceptor
is incorporating the SAAJ i
Ok, I was able to try the 2.1 release, I also commented out the explicit
SAAJ interceptor from the config file, as you suggested. I am STILL
getting the NullPointerException. I notice that the WSS4J interceptor
is incorporating the SAAJ interceptor implicitly.
BTW, why was CXF-830 closed wit
Couple more points:
* A properly escaped semi-colon (%3B) is preserved by getPathInfo.
* http://www.ietf.org/rfc/rfc2396.txt section 3.3 states that ";" delimits a
sequence of parameters in a path segment. Whatever that means. Not sure
why its dropped by getPathInfo().
* Specifying "/{id}" an
Tim Morrow 2 wrote:
Thanks for the suggestions. I could work with an upper limit of values rather
than an open ended list.
I tried @Path("/{id1};{id2};{id3}") with 3 @PathParam parameters but got a
"No operation matching request path ... is found" error.
I also tried keeping @Path("/{id}") mapp
BTW, a properly escaped semi-colon (%3B) is preserved by getPathInfo.
http://www.ietf.org/rfc/rfc2396.txt section 3.3 states that ";" delimits a
sequence of parameters in a path segment. Whatever that means. Not sure
why its dropped by getPathInfo().
I'm in over my head.
:)
Tim
Tim Morro
Thanks for the suggestions. I could work with an upper limit of values rather
than an open ended list.
I tried @Path("/{id1};{id2};{id3}") with 3 @PathParam parameters but got a
"No operation matching request path ... is found" error.
I also tried keeping @Path("/{id}") mapping to a String param
Hi group,
After successfully testing my WebService on my local PC (WinXP), I have
deployed it on to the application server running on Linux.
Upon invoking the method from my client, I am getting the below error.
Can someone help me?
I found no relevant hits in Google !!!
[09.06.08 14:34:10:169
I've ended up thoroughly going thought my classpath and resolved some
possible conflicts with CXF. everything is now working as expected.
Thanks for the support,
Daniel
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: 06 June 2008 18:44
To: users@cxf.apache.org
Subjec
Hi Sergey,
going back to your earlier email, specifically the point anbout
introspecting a given application type.yes I think this is what
I'd like to do.
At the moment I have a class with methods that return my XMLBean
objects. I now have providers for getting XML and JSON from the
XMLBean o
Hi
Would PathParam("{id1};{id2};{id3}") work ?
Or are you thinking of being able to handle a different number of product ids
per request ?
Perhaps the simpliest way would be to do
PathParam("productIds") String
and then String.split(";") in the function body
I'm not sure JAX-RS provides for
26 matches
Mail list logo
