Oh, you can't do any configuration on the bus within the cxf-servlet.xml.
Because when CXFServlet loads the cxf-servlet.xml the bus has already been
loaded.
You can use the beans.xml to do some configuration first. You can find the
example in the CXF kit's samples\java_first_spring_support
Maybe you need report a Bug for STP.
BTW,
You can't add any interceptor in the cxf-servlet.xml , it just uses for
loading the endpoints with a already initiated bus.
Willem.
Tophebboy wrote:
Yes, I'm using Eclipse STP and SOA tools.
When you generate the code from your wsdl, a web.xml and
Hi Guillaume
The AuthorizationPolicy only works for HTTP Conduit of HTTP Destination.
In your case , I don't think this policy will take effect, since CXF just
uses URL to get wsdl when create the service from wsdl.
Maybe you need to use JVM's proxy setting such as
-DproxySet=true
Hi ,
You can use WebServiceContext to get the session.
@Resource
private WebServiceContext context;
Here is an example[1][2] to show that in CXF Systest
[1] Server
--
Willem2 wrote:
Hi,
I just checked the code, it looks like you can't get the
DestinationManager from bus .
Can you show the configuration file for us to dig the problem ?
BTW, which spring version are you using?
Willem.
MyScreenName wrote:
CXF versions: 2.0.3 and 2.1
Using JAXWS
I can't tell it just from a single message.
It may relate to your log configuration, do you use log4j in your
container(tomcat) ?
Because CXF uses java.util.logger, even it is debug information, you will
get ERROR [STDERR] message.
In CXF2.0.3 we did some refactoring work in logger, you should
Hi Bruce,
I just checked the java_first_jaxws test , we definitely missed the
cxf-servlet.xml in wsdl directory.
Thank you for pointing it out , I will fix it in my next commit.
Willem.
Bruce Z wrote:
Hi Jervis,
Thanks for the reply.
I followed the instructions as described in
If you set the disable-address-updates , you also need to set the
base-address like http://localhost:8080/myapp
Since CXF servlet will not update the endpoint address with the request url,
you need to specify the base-address to build up a real accessible address
for the endpoint.
Willem.
here.
[1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/servlet/web-spring.xml
[2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/servlet/spring.xml
Willem.
ojs wrote:
Willem2 wrote:
Can
Hi Benson,
It is a CXF's XML binding, which just marshals and unmarshals the pure xml
without any SOAP header of body involved.
I think it there is no spec for it, we just implement it in CXF.
Since I am not 100% sure about that , please point me out if I am wrong.
Willem.
bmargulies wrote:
O , You just need create a CounterRepository which
will help you setup whole interceptors for the counter work now.
Here is a configuration for your:
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Now , CXFServlet always updates the endpoint's address with the request url.
You can fill a JIRA[1] with your wishes.
[1]http://issues.apache.org/jira/browse/CXF
Willem.
Christian Vest Hansen wrote:
I deploy a CXF web service to a cluster that sits behind a content switch.
We have HTTPS
Hi,
Here is a way[1] that you can specify the address per message.
[1] http://www.nabble.com/Re%3A-Client-question-p12429227.html
Willem.
tirtza wrote:
I am using spring + CXF (JaxWsProxyFactoryBean ) and need to sometimes
change the port of my target endpoint without restarting the
Hi,
We do not test the CXF on OC4J.
From the stack trace, I can see the exception is thrown form the
WSDLManagerImpl.
It looks like some thing wrong with the Xerces, please make sure the CXF kit
shipped XercersImpl 2.8.1 is not conflict with the OC4J's jars.
Willem.
Hoda Nadeem wrote:
It may be the same issue which was cased by not using the JAXWS front end
API.
Please use JaxWsProxyFactoryBean to create the JAXWS client to use.
Willem.
tirtza wrote:
Although I am actually getting a valid soap response from the service an
empty response object is returned to my client.
Hi,
This is a bug of CXF configuration which can't consumer the configuration
file at the same time with client beans creating.
You can get more information here[1].
It was fixed by DanKulp few weeks ago, and it is in the latest CXF2.0.3
SNAPSHOT now.
1.2.6 to CXF 2.0.2. A lot of issues we had with XFire 1.2.6
are gone.
Thanks!
-Miknsheng
Willem2 wrote:
Hi ,
FYI, you can find the how to set the timeout parameters here [1]
[1] http://cwiki.apache.org/CXF20DOC/client-http-transport.html
Willem.
Glen Mazza wrote:
I'm not sure how
Hi,
It may relate to the Xerces Implementation.
CXF can work with xecesImpl 2.8.1 , please make sure this jar is in your
class path.
Willem.
jwagon wrote:
I'm trying to get a simple service client running against the following
WSDL:
I used SoapUI 1.7.6 to generate the service
Hi,
You need to use the bus of the CXFServlet. You could use the CXF Servlet
transport with this bus.
Please add the below code just before Endpoint.publish(...)
Bus bus = cxf.getBus();
BusFactory.setDefaultBus(bus);
Willem.
Miguel De Anda-2 wrote:
i've got an application (my server)
I can clarify it.
It is because I don't want to right a new WSDL to reproduce your case, I
just removed the method for the SEI which generate from the original wsdl.
?wsdl 's wsdl just equals to the older wsdl in your case, and the original
wsdl equals newer wsdl in your case.
Willem.
Hi,
You can use the below code to get the conduit.
Client client = ClientProxy.getClient(soap);
HTTPConduit http =
(HTTPConduit) client.getConduit();
HTTPClientPolicy httpClientPolicy = http.getClient();
Willem.
Asleson, Ryan wrote:
Hi Willem,
The example
you guys with questions?
Willem2 wrote:
Hi,
You could turn on the validation by configuration like this[1]
[1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/distribution/src/main/release/samples/wsdl_first/cxf.xml
Willem.
Adrian C wrote:
Anyone have any ideas how to turn
Hi,
You can find more information about the JMS configuration here [1][2]
CXF wiki
[1]http://cwiki.apache.org/CXF20DOC/jms-transport.html
Unit test configuration
[2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/transports/jms/src/test/resources/jms_test_config.xml
Willem.
mule1
We have a JIRA [1] for the supporting of Spring JMS template.
[1] https://issues.apache.org/jira/browse/CXF-1101
Willem
mule1 wrote:
Hello,
I was wondering how is jms with cxf different than spring's jms using
jmstemplate? Meaning what are positive points for each of them?
--
It maybe your client servlet and server servlet share a same Application
context.
When the server servlet is refreshed, the client's Application is out of
date.
I do not read your code , I may am totally wrong.
It is just a guessing of your stack trace and notes.
Willem.
narend wrote:
Hi
Hi,
Can you fill a JIAR and attach the wsdl with it.
So we can use it as a test case for debugging.
Willem.
Dan Connelly-3 wrote:
[Again.nbsp;nbsp; Here is the orginal message.]
ame scenario as my previous post.
I now run the generated server driver
I do not think httpj configuration can do that .
Because we add the service url context when we add the servant to the Jetty
Engine.
As Benson just mentioned , I don't think a common Jetty handler can filter
all the ?wsdl request.
Maybe we need to do some hacking work in the QueryHandlerRegisty
No , there is only implementorClass attribute in the jaxws:endpoint element.
Willem.
bmargulies wrote:
Is that 'serviceClass' in the jaxws:endpoint element? If so, I'll add it
to the Wiki doc.
-Original Message-
From: Willem2 [mailto:[EMAIL PROTECTED]
Sent: Friday, October 05
using. Do you think
it might be because of jdk 1.6 ?
On 10/5/07, Willem2 [EMAIL PROTECTED] wrote:
Hi,
Can you define the below method in your implementor's interface?
void setWsContext(final WebServiceContext wsContext) ;
We could add the annotation @WebMethod(exclude = true
)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
On 10/5/07, Willem2 [EMAIL PROTECTED] wrote:
Can you show me the stack trace and try the code that I just committed
?
Willem.
blacksheep wrote
pointer exception
You said your tests were successful. Which jdk are you using. Do you
think
it might be because of jdk 1.6 ?
On 10/5/07, Willem2 [EMAIL PROTECTED] wrote:
Hi,
Can you define the below method in your implementor's interface?
void setWsContext(final
You can set the JaxWsServerFactoryBean ServiceClass attribute with the
annotated interface.
Willem.
bmargulies wrote:
I've got all my nice annotations on the interface, not on the impl.
Could some kind soul clue me in on how to tell the spring config to look
at them there
--
View
)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Thanks,
On 10/4/07, Willem2 [EMAIL PROTECTED] wrote:
Hi blacksheep,
I just committed a quick fix for CXF-1074. Can
OK, on the bright side, we have a small test case to show how to get the
exception.
I will try to dig the resource injection part then :)
Willem.
blacksheep wrote:
I did it already but no luck :(
On 10/4/07, Willem2 [EMAIL PROTECTED] wrote:
Can you try to remove the @Resource
CXF support to access the web services with get method.
Here is a example [1] for it.
[1]
https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/soap12/Soap12ClientServerTest.java
Willem.
bmargulies wrote:
Sending in a random URL provoked this.
Yes, it is weird. :(
Willem.
bmargulies wrote:
I did. When I list both listeners, CXF stops working. When I only list
the CXF listener, all is well. It is very mysterious. If that is
mysterious to you, I'll fire up my trusty debugger.
-Original Message-
From: Willem2 [mailto
AH, It is me.
Now you can add the Jetty Handler in the Jetty which is working as the
embedded http engine in CXF.
You can find more information here[1] and there is an example in the http
jetty engine unit test[2]
[1]http://cwiki.apache.org/CXF20DOC/jetty-configuration.html
Do not worry about it , it just a string :)
Willem.
bmargulies wrote:
Looking at the CodeFirstTest, why does the local: URL bother to have
localhost:9000 in it?
[BIM]
--
View this message in context:
http://www.nabble.com/Local-transport-tf4537847.html#a12978840
Sent from the
Hi Benson,
You can call bus.shutdown(true) in @After to tear down the server and the
jetty engine.
Willem.
bmargulies wrote:
Please forgive me for pasting a lot of code into here.
I'm trying to set up a unit test framework where the fixture sets up
jetty with an endpoint and some
You can find some discusses from www.nabble.com cxf forum[1].
[1]
http://www.nabble.com/forum/Search.jtp?query=saajlocal=yforum=16914matchingForums=a
Here[2] is a direct answer for you .
Hi,
You could take a look at this [1]
[1] http://www.nabble.com/Client-question-tf4357978.html#a12419843
Willem.
Pawel Janusz wrote:
Hello,
is there possibility to get WSDL addres from EndPoint ?
Pawel
--
View this message in context:
Hi Glen,
CXF is using the J2SE logging.
If you use the ant to run the sample , you could change the
logging.properties file in ${CXF_HOME}/etc/ directory.
Willem.
Glen Mazza-2 wrote:
Hello,
What is the logging system used in Apache CXF -- Log4j or J2SE logging?
Also, when I'm
-servlet.xml /
bean id=newsServiceClient
class=com.mysite.services.news.NewsService
/bean
bean id=mysiteObjectFactory
class=com.mysite.services.types.ObjectFactory/bean
/beans
Willem2 wrote:
Hi ,
It looks like the WSDLServiceFactory can 't get the WSDLManager from
Please take a look at the CXF 2.0 user doc :)
http://cwiki.apache.org/CXF20DOC/client-http-transport.html
Currently, CXF only support to set the http client's configuration with the
port name or with the wild card.
If you want all the http-conduit with same client policy, you could specify
the
Hi,
If you use the jaxws:endpoint 's implementor attribute to describe the
implementor which just a ref bean, you need to use the # as the prefix of
the bean's name.
So in your case, the jaxws:endpoint should look like this.
jaxws:endpoint id=categoryService
implementor=#categoryService
45 matches
Mail list logo