Hi all,
I'm a newbie to CXF and web services in general...
The thing is that I created a service and a client with CXF and deployed them
in JBoss, both of the service and client are working fine except that when I
re-deploy the service to JBoss I get a Address already in use Exception.
It
Great work guys with 2.0.3. Thx
2007/11/13, Daniel Kulp [EMAIL PROTECTED]:
Working on it now. It should be in the maven repository in a few
minutes. It's now in the dist dir:
http://people.apache.org/dist/incubator/cxf/
I should have the download page updated shortly and will get the
I don't think you mean a tcp/ip port, but if you do, normally the Linux
command fuser -k 8080/tcp will kill any servlet container's lock on that
port (that occasionally happens with me on Tomcat, so I have to do that,
and then restart Tomcat.)
But your question seems better suited for the JBoss
The Apache Incubator CXF team is proud to announce the availability of
the 2.0.3 release!
Apache CXF is an open source services framework. CXF helps you build
and develop services using frontend programming APIs, like JAX-WS. These
services can speak a variety of protocols such as SOAP,
Hi
I m using the 2.0.2 version, i m facing issue with wsdl generation to
include response and request with parameter part of soap header.
When i defined my service like this
@javax.jws.WebService(portName = IUserServicePort, serviceName =
IUserDetails)
@javax.xml.ws.BindingType(value =
On 11/14/07, Glen Mazza [EMAIL PROTECTED] wrote:
I don't think you mean a tcp/ip port, but if you do, normally the Linux
command fuser -k 8080/tcp will kill any servlet container's lock on that
port (that occasionally happens with me on Tomcat, so I have to do that,
and then restart Tomcat.)
Thanks Glen for the quick reply,
The port that's hold by JBoss is 9090 as the address I'm using to publish my
endpoint is http://localhost:9090/sn_categories;;
This exception happens only with the CXF war files,
For the Tomecat deployment I'll submit the result for you as soon as I finish
Dear Upendra,
First of all thanks for your reply,
But the problem comes when I re-deploy my war file because the port 9090 Which
I published my endpoint on, in the first-time deployment is locked by JBoss,
I'm sure that this port is not used by any JBoss service.
And to be sure that JBoss is
Hi,
I did it with a CFX Interceptor. The code looks a lot like my JAX-WS
Handler. The headers Map is retrieved with
message.get(Message.PROTOCOL_HEADERS). And
message.get(Message.INBOUND_MESSAGE) is used as test to select between
handleInMessage and handleOutMessage.
I had to try several
Am Mittwoch, den 14.11.2007, 18:14 +0300 schrieb Eman Ali al-Maktari [IT
Department]:
Thanks Glen for the quick reply,
The port that's hold by JBoss is 9090 as the address I'm using to publish
my endpoint is http://localhost:9090/sn_categories;;
fuser -k 9090/tcp should work for you
Eman Ali al-Maktari [IT Department] wrote:
Dear Upendra,
First of all thanks for your reply,
But the problem comes when I re-deploy my war file because the port 9090 Which I published my endpoint on, in the first-time deployment is locked by JBoss, I'm sure that this port is not used by any
Dear Glen,
I know that I can kill the process or even restart JBoss but this is going to
be the last solution, for the moment I want to see if there is a way to un-bind
this port peacefully! with no kill!!.
Dear Andrew,
I tried on both 4.0.5 and 4.2.1, both on Windows and Linux
For the
Actually I have one last issue...is it possible to not set this up as a
server implememntation but to access it like the other java MX beans?
Eg can I do something like:
ThreadMXBean tMxBean = ManagementFactory.getThreadMXBean();
tMxBean.getTotalStartedThreadCount();
I'd rather not start up
In theory, if your server and consoler are in the same JVM you do not need to
start a RMI server.
But I don't think current CXF instrument manager provide this kind of feature.
Anyway, you can fill a JIRA to add your wishes.
Willem.
-Original Message-
From: Vespa, Anthony J
If it's Mode.INOUT parameter, why it's not a Holder?
If it's possible, you can use wsdl-first approach, see what you got
James
Hi
I m using the 2.0.2 version, i m facing issue with wsdl generation to
include response and request with parameter part of soap header.
When i defined my service
Glen,
I would say +1 to reduce the number of configuration files,
James
Hello,
I'm getting confused over the server-side configuration files for CXF.
When deploying a web service in a WAR file, what is the difference
between the cxf.xml config file and the cxf-servlet.xml config file? I
+1 to reduce, and make it clearer.
CXF really rocks, but configuration is IMHO a weak point.
J-F
-Message d'origine-
De : James Mao [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 15 novembre 2007 7:56
À : cxf-user@incubator.apache.org
Objet : Re: Difference between cxf.xml and
17 matches
Mail list logo
