hi,
how can I send attachments (no mtom) from the client, is there a
possibility to specify the typ (mime or dime).
thanks Alex
Daniel Kulp schrieb:
On Mon December 14 2009 4:49:05 am Alex wrote:
hi,
I have to implement a webservice which must be able to receive attachments.
The attachment
Thank vickatvuuch,
Sorry for late reply but I was stuck on some other priorities. I will try to
implement both to see which one best suited with my requirement. Can you
please let me know how to register both(Mapper and FaultOutInterceptor) in
beans.xml. I am using Spring.
Thanks Again.
Regards,
Hi,
Let us say, I have this web method:
public String getUserName(@WebParam(name = "userId") int userId);
In WSS4JInInterceptor, I need to check the validity of userId. It seems to
me that I can get the value from the following code:
Message cxfMessage = PhaseInterceptorChain.getCurrentMe
thank you Daniel for your help,
the example you mentioned works, but I still getting warnings like:
Unchecked cast from Object to Map
I am not sure what's the recommended java version fpr apache xcf.
I'am using jdk 1.6.0.17 with apach xcf 2.2.5
Do you have any idea.
Thank you Alex
Daniel Kulp
Works like a charm! Thanks!
-Original Message-
From: Justin Edelson [mailto:justinedel...@gmail.com]
Sent: Monday, December 14, 2009 11:57 AM
To: us...@felix.apache.org
Subject: Re: DOSGi w/ Custom Type
Joel-
This is a completely random and less-than-educated guess, but have you tried
a
I don't know if this fixed the original problem, but I have the exact same
exception. And I definitely am using the appropriate servicemix version of
the jaxb-impl bundle.
osgi> packages com.sun.xml.bind.v2
Dec 14, 2009 2:49:42 PM org.apache.cxf.dosgi.dsw.hooks.AbstractClientHook
lookupDiscoveryS
On Mon December 14 2009 1:37:28 pm kiffin wrote:
> I had a typo in my previous message. It should be ServerSideException. It
> could be the cause of a SoapFault if it was originated from the server
> side.
Much like the client side, you would need to look at the "Cause" of the
WebServiceExcepti
I had a typo in my previous message. It should be ServerSideException. It
could be the cause of a SoapFault if it was originated from the server side.
Thanks,
Kiffin
dkulp wrote:
>
> On Thu December 10 2009 12:09:27 pm kiffin wrote:
>> I am porting a Metro JAXWS application to CXF. There are
Were JIRA's created for these? Are patches available?
Just wanted to make sure this doesn't get lost.
Thanks!
Dan
Daniel Feist wrote:
>
> No thoughts on this one? I'll go ahead and file JIRA's then with
> patches... not sure about test cases though, have to think about to
> reproduce
I have a problem with a 'slightly' more complex type than based Java types in
my exposed web service that doesn't seem to work.
Here's the setup:
I have a simple server that has as a return type a 'custom' type that wraps a
string for this example.
The server bundles deploy fine, and the web s
Thanks Guys!
On Fri, Dec 11, 2009 at 9:40 PM, Balaji Sankar Chopparapu <
balaji.choppar...@gmail.com> wrote:
> Hi Arik,
>
> I believe pagination is responsibility of the application but not with the
> soap/rest tool kits like CXF. I feel following entities needs to be
> supported by your service
And just in case anyone wants to see the sample:
import javax.jws.WebMethod;
import javax.jws.WebService;
import javax.servlet.ServletConfig;
import javax.servlet.ServletException;
import javax.xml.ws.Endpoint;
import org.apache.cxf.jaxws.EndpointImpl;
import org.apache.cxf.transport.servlet.CXFN
I made the test and found a useful piece of information:
// this works
EndpointImpl epi = (EndpointImpl) Endpoint.create(impl);
epi.setImplementorClass(c);
epi.publish(name);
// this does not, which is what I did originally
EndpointImpl epi = (EndpointImpl) Endpoint.create(name, impl);
epi.setImp
There really are a couple options:
1) Write a databinding - since your code already uses Stax, this usually isn't
hard. You pretty much just need to wrapper it with our Reader/Writer
interfaces. The XMLBeans or SDO databinding (sdo is on trunk only right now)
would be good starting points
On Tue December 8 2009 9:31:27 am Alexandros Karypidis wrote:
> Hi,
>
> I intend to use JAX-WS to access web services from within servlets in a
> clustered environment.
>
> Rather than create a proxy for each servlet invocation, I'd like to
> cache the client stub in the session object.
>
> Does
You are getting some Axis generated code into hte service somehow:
at org.apache.axis.AxisFault
at com.taxwareenterprise.ws.TweFault
.
That is the issue. Where did the TweFault come from?That would need to
be removed.
Dan
On Mon December 14 2009 11:15:4
On Fri December 11 2009 4:40:20 pm Alex wrote:
> hi out there,
>
> I am new to APACHE CXF and I have some questions, I hope someone will
> answer.
>
> Dose APACHE CXF support soap with attachments (SWA)?
Yes. It's mandated as part of the JAX-WS spec.
> Is it possible to realise an client cert
On Mon December 14 2009 6:02:54 am Per Otto Bergum Christensen wrote:
> The runtime cost of address=".."/> is big, i takes severarl seconds. With a lot og WS
>
> Does anyone know how du reduce this/generate classes runtime to avoid
> generating classes runtime?
Really, there isn't much that can
I was trying to find out how to fix this issue which is caused after the
generated Apache CXF code. This never happened in Axis generated Java code.
Its complaining about some annotation which I don’t understand how to fix
the same.
In LnItm.java, I see the variables defined as shown below.
dkulp wrote:
>
> That example is for a server side thing to get the headers that were sent
> in
> with the request (or add headers to the response).The
> WebServiceContext is
> really a server side thing.The client side has the RequestContext and
> ResponseContexts on the proxy objec
dkulp wrote:
>
> That example is for a server side thing to get the headers that were sent
> in
> with the request (or add headers to the response).The
> WebServiceContext is
> really a server side thing.The client side has the RequestContext and
> ResponseContexts on the proxy objec
On Mon December 14 2009 4:49:05 am Alex wrote:
> hi,
>
> I have to implement a webservice which must be able to receive attachments.
> The attachments are encoded in MIME or DIME, all attachments are send
> via SWA Soap With Attachments (not MTOM).
> I tested the webservice with SOAPUI and attache
On Fri December 11 2009 11:58:51 pm Daniel Putra wrote:
> Hi Dan
>
> I removed it and confirmed that there are no NamespaceInterceptor related
> sys.outs in the log, so it is definitely gone. Unfortunately without any
> effect, the soap xml did not change at all.
OK. That's not good. We'll pro
On Fri December 11 2009 5:14:14 pm Will Johnson wrote:
> I tried the create instead of publish route, that didn't seem to have any
> effect.
Hmm. . That's not good. Can you create a small sample that demonstrates
that and log a bug?That SHOULD have worked, I think.
> As for the ServerFac
Remove the createdFromAPI="true" flag from jaxws:endpoint.With that set,
at some point, you need to call Endpoint.publish or similar to cause it to be
published. If it's not set, CXF/Spring will create and publish the object.
Dan
On Sat December 12 2009 2:31:32 am Christopher Cheng wro
On Mon December 14 2009 10:17:01 am kenkyee wrote:
> dkulp wrote:
> > In anycase, since the wsdl sucks, you would need to drop to the API's
> > listed
> > in the FAQ. On the client side, the context would be the request
> > context:
> > ((BindingProvider)proxy).getRequestContext().put(HEADER_LIST
On Mon December 14 2009 8:43:51 am Benson Margulies wrote:
> I've got a webapp with a CXF service. When I'm doing development, I'm
> fine with the usual default wsdlLocation. However, when I deploy,
> there's a firewall.
Have you looked into the PropertyPlaceholderConfigurer things in Spring?
dkulp wrote:
>
> In anycase, since the wsdl sucks, you would need to drop to the API's
> listed
> in the FAQ. On the client side, the context would be the request
> context:
> ((BindingProvider)proxy).getRequestContext().put(HEADER_LIST, headers);
>
Yep, I'm surprised they didn't put this i
I'm a bit confused.You have defined clients which are used to invoke
services running on servers, yet your question is about defining them in the
cxf-servlet which is for setting up servers.Thus, I'm confused about what
you are trying to do.Normally, the cxf-servlet would contain
j
On Sun December 13 2009 5:59:18 pm Yognhe wrote:
> Hi,
>
> I am using to create the client. I understand that to enable
> session on client I need to set SESSION_MAINTAIN_PROPERTY to be true. My
> question is: how I should I set the property in element?
>
> Thanks,
Should be something like:
Ideally, their WSDL would have defined soap:header things in the binding and
then you could pass "-exsh true" to the code generator to add params for them
automatically. However, their wsdl doesn't seem to do that. I personally
think the hardest part of dealing with WebServices is dealing wi
karypid wrote:
>
> With JAX-WS, I think you can set a flag "header=true" in the web service
> interface. Like:
> public void someWebMethod(@WebParam(header=true) String myHeaderParam);
>
Unfortunately, I don't have control of the wsdl (it's Amazon's web service).
In the PortType.java file t
I've seen this kind of thing work fine for Hibernate things, but haven't tried
with OpenJPA. Definitely sounds like an issue on their side. Please let us
know how it works out with them and if a solution can be found.
Thanks!
Dan
On Sat December 12 2009 5:15:15 pm KARR, DAVID (ATTCINW) wro
CXF has the the basic feature, the question is just to come up with a
clean way to configure it.
On Mon, Dec 14, 2009 at 9:00 AM, Alexandros Karypidis wrote:
> Benson Margulies wrote:
>>
>> I've got a webapp with a CXF service. When I'm doing development, I'm
>> fine with the usual default wsdlLo
With JAX-WS, I think you can set a flag "header=true" in the web service
interface. Like:
public void someWebMethod(@WebParam(header=true) String myHeaderParam);
The targetNamespace/name can be added to the annotation to specify these
aspects.
In fact, if you start from WSDL, I'm pretty sure
Benson Margulies wrote:
I've got a webapp with a CXF service. When I'm doing development, I'm
fine with the usual default wsdlLocation. However, when I deploy,
there's a firewall.
Customizing the Spring app context and rebuilding the webapp is not an
attractive prospect. Has anyone come up with
I've got a webapp with a CXF service. When I'm doing development, I'm
fine with the usual default wsdlLocation. However, when I deploy,
there's a firewall.
Customizing the Spring app context and rebuilding the webapp is not an
attractive prospect. Has anyone come up with a scheme so that a
servlet
Hi,
Here is the humble experience of our team ; we have been exposing a
bunch of web services for about two years :
* SOAP and REST services are versionned via
** the endpoint url : sample
http://mycompany.com/services/UserProfileService/1.0/
** the namespace of XML entities : sample
h
Hi Gabo
You can probably try to have a single XSLT stylesheet transforming a WADL with some fixed namespace into per-service specific WADL
with the right namespace. The only thing this stylesheet will do is to capture say all http://yournamespace:* elements and copy them
to http://someservice:*
Hi,
Apologies for a late reply, I was planning to reply for a while :-)
As far as approaches toward versioning SOAP services are concerned, see [1] which Oliver also referenced in the other email and
which is being used in production and also check [2] for some general information.
[3] captures
I implemented #1 from your suggestions, and it seems to work well. Thanks!
On Mon, Dec 7, 2009 at 7:36 PM, Daniel Kulp wrote:
> On Mon December 7 2009 9:27:36 am Pavel wrote:
> > Ok, I'm a bit lost then, so I'll just state once again what I observed
> > before and read in your responses.
> >
> >
The runtime cost of is big, i takes severarl seconds. With a lot og WS
Does anyone know how du reduce this/generate classes runtime to avoid
generating classes runtime?
/perotto
hi,
I have to implement a webservice which must be able to receive attachments.
The attachments are encoded in MIME or DIME, all attachments are send
via SWA Soap With Attachments (not MTOM).
I tested the webservice with SOAPUI and attached a PDF-File to the
request, and it seems that the serve
43 matches
Mail list logo
