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
message in context:
http://cxf.547215.n5.nabble.com/newbie-question-CXFNonSpringServlet-and-ws-security-tp3248140p3250219.html
Sent from the cxf-user mailing list archive at Nabble.com.
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
stion-CXFNonSpringServlet-and-ws-security-tp3248140p3248408.html
Sent from the cxf-user mailing list archive at Nabble.com.
ic or stupid question, but any help will be appreciated.
Regards,
Bayu
--
View this message in context:
http://cxf.547215.n5.nabble.com/newbie-question-CXFNonSpringServlet-and-ws-security-tp3248140p3248140.html
Sent from the cxf-user mailing list archive at Nabble.com.
18 matches
Mail list logo
