AFAIK, that is what you need to do.
Setting the factory's address to be the String which start with jms://
will be OK.
BTW, you do not need to include the below files in your spring.configuration
import resource=classpath:META-INF/cxf/cxf-extension-local.xml /
import
Hi,
Here is a clue for your issue.
Exception in thread main java.lang.NoSuchMethodError:
javax.xml.soap.SOAPFactory.createFault()Ljavax/xml/soap/SOAPFault;
It could be another SAAJ implementation instead of SUN's SAAJ1.3 was
load in the Tomcat.
Please check the Tomcat's class path for it.
Hi
Do you use the SpringBusFactory to load the Spring configuration file ?
If not , you need to include the below files to start a soap over http
service.
import resource=classpath:META-INF/cxf/cxf.xml/
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml/
import
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 to adjust the timeout parameters--someone else can
perhaps respond to that issue.
But how long should it take your
Hi,
It is a known issue. You can found more information here[1]
[1]http://issues.apache.org/jira/browse/CXF-986
Willem.
Jean-François Daune wrote:
Creating the temp file works fine. I don't know what's wrong.
There is enough space on my disk, which uses NTFS.
I noticed that turning logging
Hi Glen,
The endpointName can map to the wsdl:port name.
I will update the wiki with it .
Willem.
Glen Mazza wrote:
Hello, does anyone know the meaning of endpointName in the
configuration sample at the top (Configuring an Endpoint) of this
page[1]? In particular, what portion of the WSDL
Hi,
Yes, I just did a quick test for it .
I saw some ActiveMQ Scheduler thread there.
But after I went through the CXF code , I am sure we close the jms
consumer connection.
I have no idea why the ActiveMQ Scheduler threads are still there after
the consumer is closed.
Willem.
MickeD wrote:
Hi
CXF provides a flexible configuration of interceptor. You can
configure the interceptor in Bus level or in Endpoint level. For you
case, I think you can define the WSS4J interceptor in your Endpoint B,
and add the SAAJ*Interceptor in the bus. In this way, the EndpointA will
not check the
Hi,
I think you can take a look at the WSDLQueryHandler in the CXF core.
You can extend it and add some security check here, then register the
Handler to the QueryHandlerRegistyImpl.
Willem.
Egor Samarkhanov wrote:
Hello !
How can I restrict access to WSDL of my service?
I don't want
Hi,
If you are using the simple front end , you need to set the
ServerFactoryBean's service wrapped attribute to be false.
Willem.
James Mao wrote:
Hi,
Try annotate the SEI with
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
Then the generated elements in the schema will
I don't find a way to set the Provider properties from JAXWS API. If you
can tell the @ServiceMode's value from the script engine, I think you
can easily pick up a annotated Provider template class.
Here is only 2 types service mode.
BTW, if you use the JaxWsServerFactoryBean to create the
Hi Gilles,
I just committed a quick fix for the issue of the CXF local transport
direct dispatch model [CXF-1107].
You can try it by using the truck version or waiting few days for the
next 2.0.3 snapshot.
Willem.
Willem Jiang wrote:
Hi,
I can reproduce the error, it definitely is a CXF
Hi,
You can use the simple front end[1] instead of jaxws front end[2].
[1]http://cwiki.apache.org/CXF20DOC/simple-frontend.html
[2]http://cwiki.apache.org/CXF20DOC/jax-ws.html
Willem.
William Leung wrote:
I am trying setup a client in vs.net.
So sad, that vs.net only reconized the XFire
The WSDL that you got from from CXF is Document/Literal Wrapped.
If you want to set it to the Document/Literal model , you need to set
the JaxWsServiceFactory's wrapped attribute to be false.
Willem.
William Leung wrote:
I am testing CXF and sadlly found that our method parameters and
Hi,
I can reproduce the error, it definitely is a CXF local transport bug.
I will investigate it later today.
Willem.
Gilles Durys wrote:
Willem Jiang wrote:
Hi, Which CXF version are you using? Can you access the service with
http transport?
I just checked the code in the trunk
It is same with the jaxws:endpoint.
You need to create a service factory bean and set it to the simple:server.
Here is an example
bean id=ReflectionServiceFactoryBean
class=org.apache.cxf.service.factory.ReflectionServiceFactoryBean
property name=wrapped value=true/
/bean
simple:server
You can specify the wsdl url to your local wsdl url.
eg. File://C:\svnwork\reg\trunk\reg\reg-ws\ws-madcap\src\wsdl\madcap.wsdl
Willem.
Jarada, Hussam wrote:
my problem is that the wsdl is not accessible from this web service url.
Jarada
From: James Mao
Hi ,
There[1] are lots of ways to specify the service URL for the client.
[1]http://www.nabble.com/Client-question-tf4357978.html#a12419843
Willem.
Martin Caslavsky wrote:
Hello,
is it possible for CXF client to specify URL where client should connect to?
Martin
Hi,
You can use the simple:server tag for it.
Here are some examples for it [1]
[1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/simple/src/test/java/org/apache/cxf/frontend/spring/servers.xml
Willem.
mule1 wrote:
Hello,
I wanted to configure my services for exposing my
Yes, I need to do some doc work on the wiki.
It is on my todo list.
Willem.
Benson Margulies wrote:
Sure, but we still need to fix the Wiki to show an example with more
useful results.
-Original Message-
From: Willem Jiang [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 07, 2007 9
Hi,
You can't reuse the service factory for two jaxws endpoints.
When the service factory create the endpoint, it will not create a new
service model if the service factory's model is already there.
You need create a new service factory for endpoint to use.
Willem.
Olvera Segura Jaime Ivan
,
I am using tx:annotation-driven/ in my spring.xml .
What's the workaround for this case ?
Thanks,
Karakoyun
On 9/28/07, Willem Jiang [EMAIL PROTECTED] wrote:
Hi ,
How do you set up your endpoint implementor?
I know there is an issue that if your implementor is came from a Spring
bean
Hi ,
I think I found the key of this issue.
It is you bean.xml's definition. If you want to define the value of
simple:[EMAIL PROTECTED] with a spring bean's reference, you need to
use the prefix '#' for the bean's name, and they should be in the same
application context.
If you take the
Hi Beanson ,
Do you run the CXF programe with the last version in the trunk?
DanK did some update of logging , I do not know if all the log are go to
use log4j.
Willem.
Benson Margulies wrote:
I've got a log4j config file as follows. Anyone have a guess as to why I
keep seeing CXF 'INFO'
Hi Benson ,
You can find the examples from AbstractJaxWsTest[1] for the unit test.
And you can also find the spring configuration files form servers.xml[2].
[1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxws/src/test/java/org/apache/cxf/jaxws/AbstractJaxWsTest.java
Hi ,
How do you set up your endpoint implementor?
I know there is an issue that if your implementor is came from a Spring
bean which is enhanced by Spirng AOP will not get any WebServiceContext
resource injected.
You can find the detail information about the JIRA here [1]
Hi ,
You do not need to change the bean.xml file.
I think your implementation has an annotation attribute of the
endpointInterface.
If you remove it, the methods in you implementor class will show up :)
Willem.
lukasK wrote:
I would like to know if it's possible to omit the interface level
Hi ,
It looks like the error was thrown form the server side when the CXF
runtime invoke the service implementor.
Do you do some extra work on you server side?
Can you show me the server side configuration files?
Willem.
mule1 wrote:
Hello Dan,
I tried several things to debug to see what
Hi
It looks like
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl is not match with
javax.xml.parsers.DocumentBuilderFactory in when WSDLManager is creating.
CXF uses xercesImpl-2.8.1.jar ,you may check it against your Web container's
runtime's class path. Maybe drop this jar in your war's
Hi ,
You could try the CXF dynamic client
http://cwiki.apache.org/CXF20DOC/dynamic-clients.html
Or SoapUI
http://www.soapui.org/
Willem.
Harshit Madania wrote:
Hi ,
I want to create SOAP Requests from the WSDL of service.
What I want to do is like dynamically creating RAW SOAP Request
Hi Roger,
If you want to use the https transport by leveraging the Servlet
transport , you do not need to specify the httpj:engine-factory in your
bean.xml.
httpj:engine-factory only take effect if you use the jetty as your http
transport engine.
After I went through your bean.xml, I can't found
Sorry, I forget to attach the url.
It is
http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
Willem.
Willem Jiang wrote:
Hi Roger,
If you want to use the https transport by leveraging the Servlet
transport , you do not need to specify the httpj:engine-factory in your
sec:exclude.*_DH_anon_.*/sec:exclude
/sec:cipherSuitesFilter
/http:tlsClientParameters
/http:conduit
--
/beans
thanks
Roger
-Original Message-
From: Willem Jiang [mailto:[EMAIL PROTECTED]
Sent: 2007年9月
Hi,
Which CXF version are you using?
Can you access the service with http transport?
I just checked the code in the trunk
XMLStreamWriter xtw = message.getContent(XMLStreamWriter.class);
* xtw.setPrefix(soapVersion.getPrefix(), soapVersion.getNamespace());
I guess the NPE is came from xtw, but
of the CXFServlet bus was described, but I did not find any info, on how the obtain this reference.
Is there maybe a way to set the default transport factory to
CXFServletTransportFactory ?
Andreas
-Ursprüngliche Nachricht-
Von: Willem Jiang [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 21
Hi,
I think you can go to cxf_zh to ask for the CXF Chinese support.
BTW CXF uses JAXB as the default data binding, you can build a Map with
the following steps[2]
[1]http://groups.google.com/group/cxf-zh
[2]http://weblogs.java.net/blog/kohsuke/archive/2005/04/xmladapter_in_j.html
Willem.
Hi Andreas,
From your stack trace , I think you did not use the right bus when you
publish the endpoint.
Because it uses the JettyHttpTransportFactory , not the
CXFServletTransportFactory
Can you get the CXFServlet's reference cxfServlet?
If so , you can take a look at this blew codes, which
Hi,
I think you need to look up your class path if there any spring related
class.
Here is part of CXFServlet init code:
String springCls =
org.springframework.context.ApplicationContext;
try {
ClassLoaderUtils.loadClass(springCls, getClass());
How about try to put the saaj*.jar to the jboss lib's endorsed directory?
Willem.
Axel Becker wrote:
Hello,
i wrote a small webapplikation to display some small webservice results.
but on the first call i got these error
javax.xml.ws.WebServiceException: Cannot create SAAJ factory instance.
Hi,
I don't think it can be done by adding the interceptor now , because CXF
HttpConduit [1] just holds the cookies as it's member variable.
And for each Client proxy, CXF will set up a different HttpConduit for
the http connection.
If you want to accomplish the task, you need do some
Hi
I just went through the code and Xfire JIRA, it may relate to the
different send and receive thread on the client side.
You just need to add this pair
(org.apache.cxf.transport.local.LocalConduit.directDispatch, true) in
your request context,
to let the LocalConduit not fork a new thread
Hi
It looks like the servlet transport factory did not set up the transport
id for you to use.
If you just want CXF Servlet to use the CXFBusFactory , you can add this
option
-Dorg.apache.cxf.bus.factory=org.apache.cxf.bus.CXFBusFactory to your
WebContainer's start up script.
Willem.
Hi,
I just check the stack trace , current CXF trunk add a null pointer
checker at that point , can you try the latest SNAPSHOT?
If you want to use the ServletTransport with the simple front end API,
you still need to add the CXFServlet into you web.xml.
The cxf-servlet.xml just contains the
Hi Matt
I did not see any url in your mail below :(.
Could you send them again ?
Willem.
mattmadhavan wrote:
Hello All,
Please refer to this blog. Seems to be one of the most popular blog. Please
look at the client code! (Test case).
Any ideas? If some one has a complete ACEGI security
FYI , this blog shows you how to use HashMap in the JAXB.
http://weblogs.java.net/blog/kohsuke/archive/2005/04/xmladapter_in_j.html
Willem.
James Mao wrote:
Jaxb is quite plugable, you can use XmlTypeAdapter to marshal/unarshal
to/from HashMap
James
HashMap is not supported by JAXB binding.
Hi Ramanand,
It is [1], and you can find more information about CXF from its official
wiki [2]
[1]http://issues.apache.org/jira/browse/CXF
[2]http://cwiki.apache.org/CXF/
Willem.
Singh, Ramanand wrote:
Glen,
What is the URL for creating JIRA?
All,
Does anybody know why I am getting the
Hi,
I think Dan just show a way (some CXF internal API) to get your EJB
object be called. It don't relaid on the NumberServiceSessionBeanProxy
(Spring EJB stuff).
I just went through the code , now the EJBInvoker is not bundled with
CXF, you need to add it by yourself.
I think you will not
Hi Kevin,
You need to include the cxf-rt-transports-http-jetty-*-incubator.jar in
you class path, or add the cxf-rt-transports-http-jetty dependency in
you pom.xml.
Willem.
kevin Wong wrote:
Hi,
I am trying to create a client, com.none.SportsClient. When I ran it, the
following
JUST FYI ,
Here is a related thread[1] in the CXF Chinese Google group cxf-zh.
[1]
http://groups.google.com/group/cxf-zh/browse_thread/thread/5a31ac860999df2
Willem.
william_w_hu wrote:
I'm using apache-cxf-2.0.1-incubaor and WebLogic Server 9.2. I was able to
run the helloworld sample
Hi Ramanand
Can you tell us the Spring version and CXF version that you currently use?
I just checked the code, CXF trunk version and Spring 2.0.4, there are
no any final method definitions of getIdOrName in BusDefinitionParser or
its parent class.
It is just
protected String
Hi ,
You can get the HttpConduit with these codes after creating the service
object.
Client client = ClientProxy.getClient(service);
HttpConduit conduit = (HttpConduit) client.getConduit();
Willem.
Chris Campbell wrote:
I cannot figure out how to use SSL in a simple front end client like
Hi,
The web.xml just help you to set up the servlet transport for the CXF
runtime.
If you want to publish your service you still need to some thing like
the wiki [1]said.
Such as write the cxf-servlet.xml or write the code using JAXWS API or
CXF ServerFactoryBean.
And there is another
of the
beans.xml file, but I still have the same error as before. i.e. it doesn't
seem to have preloaded the depends-on bean.
thanks again
Doug
On Thursday 06 September 2007 17:56, Willem Jiang wrote:
Hi doug ,
I just committed a patch CXF-955 which is contributed by Fred into the
trunk.
It added
Hi,
The commons logging issue should be missing the commons-logging-1.1.jar
in the CXF lib directory.
Willem.
Jon Mountjoy wrote:
WebLogic Server has an interesting prefer-web-inf-classes setting
that you can define which changes its default class loader behaviour -
see
Hi Ryan ,
It is wired because there is only one difference in the the transport
layer between the http and https.
So I am wonder whether you create two different projects (one for http ,
the other for https) or not.
Maybe there are some difference between your two projects setting.
Willem.
Hi Ryan,
We are just voting 2.0.2 in the cxf-dev, you can get staged kit from [1]
[1]http://people.apache.org/~dkulp/stage_cxf/2.0.2-incubator-take1/
Willem.
Ryan Moquin wrote:
No problem. Do you have any idea how stable 2.1 is? I notice that my issue
with the IndexOutOfBounds with the
of that is, but it adds about
2 to 5 minutes to the startup time of the applet.
Also, the jar file was already downloaded and cached by the JRE.
Any insights into this one would be much appreciated!
Thanks again
Doug
On Wednesday 12 September 2007 11:55, Willem Jiang wrote:
Hi Doug,
After I
occurs on 2.1. I can see if I
can get a test case to demonstrate this as well.
On 9/11/07, Willem Jiang [EMAIL PROTECTED] wrote:
Hi Ryan ,
It is wired because there is only one difference in the the transport
layer between the http and https.
So I am wonder whether you create two different
Hi
It looks like that wstx can't consume the incoming message.
Can you try to call the service without the SSL socket wrap first?
And there also another question, how did you generate the client side
artifacts ?
We need to find out the issue come from the SSL configuration or from
the wired
Hi Ryan,
I don't know if you had resolved theh SSL configuration issue. You
configuration file looks good to me.
I just went through the stack trace, I found it caused by a soap header
build up problem.
Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at
Hi Ryan,
Can you tell me how you generate the soap header message with the wsdl2java?
Did you specify the option -exsh true when you call wsdl2java?
If not , please try it again.
Willem.
Ryan Moquin wrote:
I actually just got my breakpoint to be hit:
It's choking on an element of my WSDL
/wsdl:definitions
On 9/10/07, Willem Jiang [EMAIL PROTECTED] wrote:
Hi Ryan,
Can you tell me how you generate the soap header message with the
wsdl2java?
Did you specify the option -exsh true when you call wsdl2java?
If not , please try it again.
Willem.
Ryan Moquin wrote:
I actually just got my
Hi
If you use the Jaxws API getPort to create the client proxy. CXF will
try to get a default bus first ,
if the default bus is not exit, it will create a bus and set default bus
and default thread local bus for you.
So the thread local object in your case should be the bus :)
Here are some
Hi doug ,
I just committed a patch CXF-955 which is contributed by Fred into the
trunk.
It added the depends-on attribute in the jaxws:endpoint. I think you
just want that :)
You can try latest version in the trunk , or wait for the next snapshot.
Willem.
doug wrote:
I have implemented some
HTTPS
appropriately at runtime.
So, how can I do this? How can I replace the http:conduit element with
a set of API calls?
2007/9/5, Christian Vest Hansen [EMAIL PROTECTED]:
Thanks!
Renaming beans.xml to cxf.xml seams suitable to my situation :)
2007/9/5, Willem Jiang [EMAIL PROTECTED
Hi,
Here is an example for you :)
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xmlns:soap=http://cxf.apache.org/bindings/soap;
xsi:schemaLocation=
Hi Burki,
This issue is caused by current CXF bus will not load the configuration
when the clients are created from spring configuration. Here is a
JIRA[1] for tracing it, currently I provide a walk around method in the
JIRA comments. I think it will take some time to really fix it after we
Hi , yogen,
First how can you tell the CXF did not pick up the configuration file ?
Can you show me the log for it.
If you read the log to get the information, then please check your class
path with these two things:
1. Spring* jars are in your class path.
Because you use the JAXWS API to
Hi,
You could name the beans.xml to cxf.xml and put it into the class path.
CXF will load it automatically.
You could also use -Dcxf.config.file=beans.xml load the configuration
file in the class path,
or you could use -Dcxf.config.file.url={beans.xml url} to load the
configuration file.
Hi ,
If you are want to look up the user credentials in an interceptor, you
could use the below codes
public void handleMessage(Message message) throws Fault {
AuthorizationPolicy policy =
message.getContent(AuthorizationPolicy.class);
...
}
Willem.
Daniel Kulp wrote:
On Tuesday
Hi
For the Server side
If you are using the JAXS API , you can Endpoint.publish() the service
with different address.
Object implementor1 = new AnonymousComplexTypeImpl();
String address = http://localhost:9000/anonymous_complex_typeSOAP;;
Endpoint.publish(address, implementor1);
If you are
Hi
CXF will load the cxf.xml as the default configuration file from the
class path.
If your configuration file's name is services.xml you need to specify it
with java command line option
-Dcxf.config.file=some_other_config.xml or load the configuration file
with SpringBusFactory first.
Hi Frankie,
It just looks like there is no observer of
http://localhost/website2/ws/HelloWorld;,
No I can't figure out the reason of this issue, the configuration is right.
Please check the below things:
1. Does your war name be website2.war ?
2. Can you tell the version number of the CXF
OK,
The exception was thrown from the jaxb, so please check the JAXB jars in
you class path.
Are you using JDK 1.6 ? Current CXF just use JAXB 2.0.5.
BTW
Please try CXF 2.0.1 or the latest snap shot , there are lots of bug
fixings beyond the CXF 2.0.
Willem.
FrankieHuang wrote:
Hi Willem,
Hi ,
It looks like the WSDLServiceFactory can 't get the WSDLManager from
the bus when you try to create a service model for the client.
public WSDLServiceFactory(Bus b, String url, QName sn) {
setBus(b);
try {
// use wsdl manager to parse wsdl or get cached
Hi ,
I just answer the get source(IP) address question, because Jervis has
showed your the code how to get the wsdl operation.
You can get the client request object from the message context. Then you
can get the client address from the request.
Here are the code snaps
HttpServletRequest
Hi,
If you use JAXWS API , you can using the add port to add the other port
for your client to access.
URL wsdlURL = MyService.class.getClassLoader.getResource(service2.wsdl);
QName serviceName = new QName(urn:service2, MyService);
QName portName = new QName(urn:service2, ServicePort);
Hi Frankie
Current CXF does not support to get the service list with the
?serviceList,
I think you can get the service list with this url
http://localhost/website2/ws/HelloWorld/services
Willem.
FrankieHuang wrote:
Hi Willem2,
I got the similar question, but can not resolve it
Hi,
If you use the jetty http transport, jetty will use BoundedThreadPool
as the default thread pool.
If you want to take control of the Jetty's thread number, here is a doc
for it.
[1] http://cwiki.apache.org/CXF20DOC/jetty-configuration.html
Willem
Yadav, Yogendra (IT) wrote:
Hi,
I am
Hi Yogen,
If you take a look at the code (ServiceInvokerInterceptor) , CXF just
use the JAXWS specified executor when it dispatch the call to the
implementor object.
And the most of the works ( marshaling/ unmarshaling the messages by the
intercepter chain) are done in the transport thread.
Hi,
You can take a look of the below two documents.
[1] http://cwiki.apache.org/CXF20DOC/mtom.html
[2]http://cwiki.apache.org/CXF20DOC/mtom-attachments.html
And you can find the simple MTOM from CXF bin distribution .
Willem.
Pawel Janusz wrote:
Hello,
I'm starting using CXF to use them as
Hi
I found your fault , you misspelling the CXFServlet by CFXServlet.
Your web.xml should be
!-- CXF Web Services --
servlet
servlet-nameCXFServlet/servlet-name
servlet-classorg.apache.cxf.transport.servlet.CXFServlet/servlet-class
load-on-startup1/load-on-startup
Hi
Please see my comment in the mail.
Fred Dushin wrote:
On Aug 20, 2007, at 6:15 AM, Christian Vest Hansen wrote:
Hi,
I don't get why I must do all this configuration of cxf in order to
make it access external web services over HTTPS when my web browser is
able to access web sites over
Hi,
You can take [1]'s inlineSoapBinding bean as a example to configure the
MTOM on the client side.
[1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxws/src/test/java/org/apache/cxf/jaxws/spring/clients.xml
Willem.
nuka wrote:
I didn't configure MTOM on the client
Hi
It looks like the Service Name is not a right one from the exception's
message.
Please check the Service QName with the wsdl which you get from the
http://192.168.98.46:8080/pfc/services/PfC?wsdl
Willem.
doug wrote:
Hi,
I think I have my server set up ok because if I visit this page:
soap:address location=http://192.168.98.46:8080/pfc/services/PfC/
/wsdl:port
/wsdl:service
/wsdl:definitions
On Wednesday 22 August 2007 13:10, Willem Jiang wrote:
Hi
It looks like the Service Name is not a right one from the exception's
message.
Please check the Service QName
Hi,
The conduit name should be the port's Qname + .http-conduit
http:conduit
name={http://client.webservice.crm.ecot.com/ws/student}StudentService.http-conduit;
In your configuration, it looks like the http:conduit's name attribute
is set to be the service's Qname + .http-conduit
Hi Benson,
Please see the comments in the mail.
Benson Margulies wrote:
I've just used wsdl2java in CXF for the first time. My goal here is to
migrate an existing service from a C++ web service toolkit to CXF. While
I'm starting with an existing WSDL, from here I'd like to treat the
generated
-
Fra: Willem Jiang [mailto:[EMAIL PROTECTED]
Sendt: 8. august 2007 08:56
Til: Morten Andersen; cxf-user@incubator.apache.org
Emne: Re: Multiple JMS services
Hi ,
I just went through the code, and so did some experiments. JMS's
EndpointInfo is not just came from the Endpoint.publish
Hi Kevin,
I think you just make sure the service class which you passed to the
JaxWsserviceFactoryBean get the right jra annotation.
That can address your concern :)
Willem.
kevin.shen wrote:
if i write the jra annotations in interface , and JaxWsserviceFactoryBean use
implementor to get
Hi Michelle
If you do not pass the wsdl location to CXF when you start up the service,
CXF will try to build a service model form the service class. You can
find more information about the service model from this URL [1].
I have no idea about your last question's automatic way. Can you
Hi Julian ,
Current CXF not support the rpc encoded message mode.
Willem.
Julian Kölle wrote:
Sorry, this did not help.
Of course I was using an URL. the the-client.wsdl was just a placeholder.
If you want to try here are some WSDL's I tried and that result in Exceptions
with CXF
Hi ,
I am afraid you still need to pass the wsdl to the service factory bean.
Because current CXF JMS transport just get the JMS address information
from the WSDL extension.
Willem.
mule1 wrote:
Hello,
I am new to cxf and have creating web service using simple:server
configuration exposing
=HelloWorldImplService
wsdl:port binding=ns1:HelloWorldImplServiceSoapBinding
name=HelloWorldImplPort
soap:address location=http://localhost:8080/cxfs/ws/HelloWorld/
/wsdl:port
/wsdl:service
So where am I messing up?
Thanks.
Mark
Willem Jiang-2 wrote:
Hi Mark,
It's my fault
/}HelloWorldImplService.http-conduit;
http-conf:client Connection=Keep-Alive
ProxyServer=localhost
ProxyServerPort=
AllowChunking=false /
/http-conf:conduit
/beans
Thanks.
Mark
Willem Jiang-2 wrote:
Hi
Hi Andersen,
As you know the Endpoint.publish(address1, implementor1) 's address1 can
be any string, and it will take no effect if you just use the jms
transport.
Because the JMS endpoint address information is got from the wsdl.
So back to your question. I just checked the codes, and found
Hi Mark,
You need to do some conduit setting work[1].
The proxy server setting could be
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:http-conf=http://cxf.apache.org/transports/http/configuration;
Hi ,
Which version of CXF are you using?
Can I have a look at your client side test code?
It looks like the connection between the client and server is broken
from your stack trace. It may be the client exited before the server
sent response back.
Did you use the tcpmon[1] to catch the
Hi ,
I am sorry to reply your letter so late. If you still not find a
solution yet, please take a look at my suggestion.
Yes, CXFServlet will try to load a bus without spring support.
But before you use the JAXWS Endpoint.publish() API , you need to setup
the default bus with the CXFServlet
Hi Bruno,
Please use the below url to access your service. You may also study the
hello_world samples' readme for more detail information.
http://localhost:8000/{your war's name}/services/book
You just need to replace the {your war's name} with the your war's name.
Willem.
Verachten Bruno
101 - 200 of 252 matches
Mail list logo