Thanks a lot Dan, your fix worked. Now we can run our complete test suite
again. Using CXF 2.0.2, not sure but, I remember having
"cxf-rt-transports-http-jetty" artefact on classpath without specifying
explicitly in the POM what is now neccessary for 2.0.4. Also not sure about
the spring import de
Hi,
I am able to deploy my webserice in tomcat as well as JBoss.
But I am getting the following error when i deployed the same war in weblogic
9.2
(WSDLManagerImpl.java:97)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for com
When you tried to deploy to Weblogic, did you attempt to deploy as a
bare WAR, or wrapped in an EAR? You need to deploy as an EAR.
The descriptor setup is documented here:
http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-WebL
ogic
However, when I tried it on WLS-9.2.2, I got
Hi,
I am able to deploy my webserice in tomcat as well as JBoss.
But I am getting the following error when i deployed the same war in weblogic
9.2
(WSDLManagerImpl.java:97)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
Truncated. see lo
I was able to load my cxf app on WLS-9.2.2 and access the WSDL (havn't
tested services
yet)
I followed the instructions here:
http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-Pack
warinanear%252Cdeploytheearwithweblogicapplication.xml
With a slightly modified weblogic-applicat
I am getting the same problem eventhough i deploy it as an ear file.
java.lang.ClassCastException: interface
org.xmlsoap.schemas.wsdl.http.AddressType
I followed the steps mentioned in
http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-WebLogic
Regards
-Binu
- Origina
Hi Ayush,
I haven't tried with Netowork of brokers but I know how we connect to
the JMS broker and the configuration that you have provided in the mail
should work although it hasn't been tested in CXF as of yet. We do not
mess around the connection properties that are specific to JMS broker s
Can you try with the 2.0.5 SNAPSHOT?
Due to a bug in 2.0.4, only a single cookie is maintained on the client
side. Thus, if you have mulitple cookies, they won't all be maintained
and sent back. This is fixed with 2.0.5.
The alternitive is to use a session on the server side. The only cook
I will try it.
BTW, is this the best way to deal with cookies on the *server* side?
My concern is it is not portable. Thanks.
@Resource
public void setWebServiceContext(WebServiceContext ctx) {
context = ctx;
}
//Resource
public WebServiceContext getWebServiceContext() {
Maybe you can try adding :
org.xmlsoap.*
to the weblogic-application.xml I sent earlier.
-Chris
-Original Message-
From: Binu Andrews [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2008 8:52 AM
To: cxf-user@incubator.apache.org; Wolf, Chris (IT)
Subject: Re: Getting error wh
BTW, the code below does not seem to work on Weblogic-9.2.2, although it
works
on Tomcat-5.5, and it sort of works on the embedded Jetty (except really
long cookie
values seems to get truncated.)
-Original Message-
From: Wolf, Chris (IT)
Sent: Tuesday, March 11, 2008 10:05 AM
To: Daniel
On Tuesday 11 March 2008, Wolf, Chris (IT) wrote:
> I will try it.
>
> BTW, is this the best way to deal with cookies on the *server* side?
> My concern is it is not portable. Thanks.
Well, to make it portable, just change the keys:
AbstractHTTPDestination.HTTP_REQUEST and
AbstractHTTPDestinatio
In my application, I was not able to get CXF and Tomcat to share the (TCP)
port 8080. Is there some trick I'm missing, or is it actually impossible?
Also, how can two distinct services share the same endpoint URL?
Regards,
Scott
On Mon, Mar 10, 2008 at 3:26 PM, Norman Barker <[EMAIL PROTECTED]>
wr
I used a nightly build (from SVN), and then I generated the war with
same structure as 'ant war' with the wsdl first sample in the
distribution. It sounds like you are trying the to run the test
server jetty and tomcat together which won't work. Copy the generated
war to tomcat\webapps.
I believ
Yes, I was able to fix wsdl2java by adding the exclusion below.. but there
are now further issues when trying to run a client:
Exclusion:
commons-configuration
commons-configuration
1.4
15 matches
Mail list logo