al Message-
> > From: Emiliano Carlesi [mailto:emiliano.carl...@itattitude.com]
> > Sent: Mittwoch, 6. November 2013 11:57
> > To: users@cxf.apache.org
> > Cc: Andrei Shakirin; Emiliano Carlesi
> > Subject: RE: Newbie question
> >
> > Hi Andrei,
> >
> >
13 11:57
> To: users@cxf.apache.org
> Cc: Andrei Shakirin; Emiliano Carlesi
> Subject: RE: Newbie question
>
> Hi Andrei,
>
> As first, thanks for your replies.
>
> Yes. I don't want to have, client side, any configuration . I want to use only
> the informations obtain
shaki...@talend.com]
Sent: Wednesday, November 6, 2013 11:52 AM
To: users@cxf.apache.org
Cc: Emiliano Carlesi
Subject: RE: Newbie question
Hi,
Just re-reading your message, would you like that WS-Policy with security
assertions is not stored locally by the client, but will be retrieved fro
Hi,
Just re-reading your message, would you like that WS-Policy with security
assertions is not stored locally by the client, but will be retrieved from the
service?
Regards,
Andrei.
> -Original Message-
> From: Emiliano Carlesi [mailto:emiliano.carl...@itattitude.com]
> Sent: Dienstag
Hi,
Scenario should work in CXF out of the box.
You can start from this Glen's blog:
http://www.jroller.com/gmazza/entry/cxf_sts_tutorial .
After make it working, try to add MEX attribute in your policy assertion.
Regards,
Andrei.
> -Original Message-
> From: Emiliano Carlesi [mailto:em
Thanks Jeff, your suggestion worked
--
View this message in context:
http://cxf.547215.n5.nabble.com/Newbie-Question-WARNING-No-root-resource-matching-request-path-has-been-found-tp5098573p5105681.html
Sent from the cxf-user mailing list archive at Nabble.com.
On 25/12/11 22:36, Jeff Wang wrote:
instead of:
try
the CXF servlet is matching /*, and your url base is /cxftest (which
is the name of your deployed war, I assume.) CXF can't find
/myService/customer/1 because you have declared /customer/1 instead.
Thanks Jeff for this tip,
Sergey
Hi,
I'm a newbie too, but my cxf conf works and I noticed the server URL is hard
coded:
http://${ws.server.url}:8080/${ws.context.url}/ws/";>
instead of:
try
the CXF servlet is matching /*, and your url base is /cxftest (which
is the name of your deployed war, I assume.) CXF can't find
/myService/customer/1 because you have declared /customer/1 instead.
Jeff
On Fri, Dec 23, 2011 at 8:01 PM, cxfuser wrote:
> Hello
>
> I'm trying
On Tuesday 09 November 2010 6:13:58 am Bayu Anggorojati wrote:
> On 08-11-2010 22:07, Daniel Kulp wrote:
> Hi Dan,
>
> Thank you for your response. I will answer to your suggestions below.
>
> > Don't remove the whole thing, just the two xmlsoap.org namespaces above.
> > Those are basically telli
On 08-11-2010 22:07, Daniel Kulp wrote:
Hi Dan,
Thank you for your response. I will answer to your suggestions below.
Don't remove the whole thing, just the two xmlsoap.org namespaces above.
Those are basically telling the runtime that whenever those namespaces are
encountered, use the local tr
On Friday 05 November 2010 1:56:49 pm Bayu Anggorojati wrote:
> Hi Dan,
>
> Thank you for your highlight. I checked the applicationContext.xml, and
> there is these lines of codes for configuring CXF web service:
>
> implementor="#queryOperationsWebService" address="/" />
> implementor="#que
Hi Dan,
Thank you for your highlight. I checked the applicationContext.xml, and
there is these lines of codes for configuring CXF web service:
implementor="#queryOperationsWebService" address="/" />
implementor="#queryOperationsWebService" address="local://query" />
lazy-init="false"
Well, the main issue is:
> [org.apache.cxf.transport.local.LocalTransportFactory:106] - Creating
> destination for address /
All the destinations that are being created are on the LocalTransport, not the
http stuff. Thus, it wouldn't be available on the servlet stuff. I would
check the conf
Hi Dan,
I just want to add my previous post. I found somewhere in this forum,
almost the same problem but in different context. Someone said that
there might be jax-ws conflict. I don't really know what might caused
the conflict, but from the previous log that I sent out, I found the
followin
Hi Dan,
Here is the log at the start up, but it is very huge:
###
INFO (2010-11-05 11:51:36,153
[org.fosstrak.epcis.repository.RepositoryContextListener:76] - Starting
Fosstrak EPCIS Repository application
INFO (2010-11-
On Thursday 04 November 2010 11:15:15 am viveksvl wrote:
> Dan, Bayu,
> This is just to confirm my understanding, When you do WSDL2Java for a wsdl
> that has security policy, it does not generate the call back handlers(or
> inerceptors) correct? Meaning, I do see the JAXB components, Server(Service
On Thursday 04 November 2010 12:57:32 pm Bayu Anggorojati wrote:
> Hi Dan,
>
> Thank you for your response. I endorse the JAXB 2.2 API jar, and the
> wsdl2java works now.
>
> However I faced another problem. When I try to access the web service
> application after it is being deployed on tomcat,
Hi Dan,
Thank you for your response. I endorse the JAXB 2.2 API jar, and the
wsdl2java works now.
However I faced another problem. When I try to access the web service
application after it is being deployed on tomcat, I got the following
error/message "No services have been found."
Do you
Dan, Bayu,
This is just to confirm my understanding, When you do WSDL2Java for a wsdl
that has security policy, it does not generate the call back handlers(or
inerceptors) correct? Meaning, I do see the JAXB components, Server(Service
class), Client. Please confirm.
Thanks,
Vivek.
--
View this
Well, there are three potential workarounds for this:
1) Endorse the JAXB 2.2 API jar.
2) Use Java 5 instead of Java 6
3) Drop the jaxb-impl and jaxb-xjc jars down to 2.1.13 instead of 2.2.
I'll have to see if there is an easier way to detect this (other than an
UndeclaredThrowableException
Here is the full stack trace:
org.apache.cxf.tools.common.ToolException:
java.lang.reflect.UndeclaredThrowableException
at
org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:279)
at
org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
On Thursday 04 November 2010 8:08:57 am Bayu Anggorojati wrote:
> Hi Dan,
>
> I encountered this error when trying to generate the java code from wsdl
> using wsdl2java from cfx 2.3.0:
>
> WSDLToJava Error: java.lang.reflect.UndeclaredThrowableException
>
> I never had this error with 2.2.10 at
Hi Dan,
I encountered this error when trying to generate the java code from wsdl
using wsdl2java from cfx 2.3.0:
WSDLToJava Error: java.lang.reflect.UndeclaredThrowableException
I never had this error with 2.2.10 at least. Is it a bug? or is there
any thing that I need to take care of in 2.3
What version of CXF? At one point, there was a bug where interceptors added
to the endpoint directly didn't get added to the chain. Make sure you are
using 2.3.0.
Also, in your code below, you are not setting any actions on the
Wss4jInInterceptor. Thus, it may be bailing out fast as its n
When I debugged it, it just went directly to the port implementation method,
i.e. it didn't go to the callback-handler class.. does anybody know what
might go wrong in this case?
Thank you in advance.
bayu
--
View this message in context:
http://cxf.547215.n5.nabble.com/newbie-question-CXFNon
jaybytez wrote:
>
> 1) The wsdl_first example contains a cxf-servlet.xml and
> server-applicationContext.xml, while the cxf-jaxws-javafirst archetype
> creates a project with a beans.xml and web.xml file. Is it an either or
> approach? If you pair a Spring applicationContext.xml with a
> cxf-s
Hi Philippe,
I already found out what I did wrong.
Because the webapp uses Jetty, there was a second spring-web.xml and that
file didn' t contain the correct info.
When I added the correct info, it worked.
Ted
2010/6/30 antoine philippe chaker
> Hi Ted,
>
> i'm a newbie too :-) but could you gi
Hi Ted,
i'm a newbie too :-) but could you give us the complete url that you try to
call ?
Philippe
2010/6/30 Ted Roeloffzen
> Hi All,
> I have a quick question.
> I'm using cxf 2.2.3 and I want to register a service (the server side) via
> Spring.
> My web.xml contains
>
> contextConfigLoc
Interceptor tutorial:
http://www.jroller.com/gmazza/entry/jaxwshandlers_to_cxfinterceptors (which
links to the JAX-WS handler tutorial, both provide opportunities to get to
HTTP and SOAP headers.)
Glen
Gabo Manuel wrote:
>
> Hi Ted,
>
> Try:
>
> message.getExchange() from an interceptor
>
>
Hi Ted,
Try:
message.getExchange() from an interceptor
or
PhaseInterceptorChain.getCurrentMessage().getExchange() for a more
generic approach.
If you really need access to the session, afaik, the Exchange object has
a getter for the session.
Not sure if this answers your question.
Gabo
Ok, classpath incorrectly set up, this is what was tripping me up.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2008 1:24 PM
To: users@cxf.apache.org
Subject: RE: Newbie question on running the CXF Samples in Eclipse
I am not even
" gives the same result.
Like I said, I suspect it is something really simple that I am missing.
sgg
-Original Message-
From: Ostermueller, Erik [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2008 12:25 PM
To: users@cxf.apache.org
Subject: RE: Newbie question on running
Use eclipse to start tomcat.
Then, put breakpoints in your client and/or server code.
>From inside eclipse, run the client.
It should stop at the breakpoints you've set.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2008 11:22 AM
To: us
34 matches
Mail list logo
