Hi all,
I have created a web service and followed the instructions in
http://cwiki.apache.org/CXF20DOC/servlet-transport.html in order to deploy
it in JBoss. I am publishing the end point using the XML. As mentioned in
the instructions, i added edited the web.xml with the servelt information
and
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 feature off is a workaround.
I can live with it. I'll wait for 2.0.3 release.
J-F
-Message d'origine-
De : Daniel Kulp [mailto:[EMAIL
Can you check the following files on your classpath ?
META-INF/spring.handlers
META-INF/spring.schemas
-Jim
shaminda perera wrote:
Hi all,
I have created a web service and followed the instructions in
http://cwiki.apache.org/CXF20DOC/servlet-transport.html in order to deploy
it in JBoss. I
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
Jim, yes I have those files in the classpath. I mean they are inside the
spring-beans-2.0-m2.jar\META-INF folder. this spring jar is in the
classpath.
These files should be in cxf-rt-frontend-jaxws.jar. And jaxws.xsd is
also packaged into this jar file. Can you
confirm this jar file on
Hi Jim,
Thanks again,,
updating the spring version to 2.0.6 did the trick..
now that error is not coming...
however,, now i am getting the following error:
11:50:41,860 ERROR [STDERR] 18-Oct-2007 11:50:41
org.apache.cxf.service.factory.ReflectionServiceFactoryBean buildServic
eFromClass
INFO:
11:50:42,892 INFO [STDOUT] 11:50:42,892 ERROR [ContextLoader] Context
initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'companyTrackSearch': Invocation o
f init method failed; nested exception is java.lang.ClassCastException:
It seems
This is my full services.xml file contents :
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
Hi,
When I see the ClassCastException, the ClassLoader issue would pop
up in my mind.. ;-), I stuck with the classloader issues these days.
Can you show how you deploy the cxf libraries? put the required jars in
the war, and then deploy the war to JBoss with scoping classloader? I am
Hi !
I haven't found any documentation on how to work with faults
in CXF. Am I missing something?
Please let me know how to declare my own fault in my service?
Do I need to extend some base class (exception) to create my
own fault? What if I don't use Aegis binding?
Thanks,
Egor Samarkhanov
shaminda perera wrote:
Yes, i put the CXF libraries in the war file. and then use maven to deploy a
EAR file which contains the war file.
Does JBoss have a JAXB jar file? if so where can i locate it?
$JBOSS_HOME/lib has jaxb-api.jar and jaxb-impl.jar.
regards,
Andrew Dinn
---
Hi,
The simple way to verify whether it is the JAXB jar issue, you can put
the jaxb-api, jaxb-impl in the $JBoss_HOME/lib/endorsed folder,
and then see if it works or not.
If it is the issue, you might need to refer to the this [1] to see how
to configure a scoped classloader in JBoss to
It is jaxb jar issue . FYI :
http://forums.java.net/jive/message.jspa?messageID=212259 .
-Jim
Jeff Yu wrote:
Hi,
The simple way to verify whether it is the JAXB jar issue, you can put
the jaxb-api, jaxb-impl in the $JBoss_HOME/lib/endorsed folder,
and then see if it works or not.
If it
I put the jaxb jars to \lib\endorsed.
and now its working fine. I mean that error which cam earlier is not
coming..
however,, the spring context is not getting started because of another
(unrelated) error
This is the error log..
13:10:16,890 INFO [Lifecycle] starting up:
jboss-el.jar is missing? It looks like a jboss issue , you can ask
jboss mailing list .
-Jim.
shaminda perera wrote:
I put the jaxb jars to \lib\endorsed.
and now its working fine. I mean that error which cam earlier is not
coming..
however,, the spring context is not getting started
Hi all,
i would add some handlers to my service.
i add
@HandlerChain(file=handlers.xml)
and i put in the same path of service class the handlers.xml file:
?xml version=1.0 encoding=UTF-8?
jws:handler-chains xmlns:jws=http://java.sun.com/xml/ns/javaee;
jws:handler-chain
I was surprised to see that JAXB schematizes the private static final
long serialVersionUID from my exception class. Is there some special
case for these, in spite of being private?
Hi !
I have a simple exception class:
@WebFault(name = faultDetail)
public class NotLoggedInException extends Exception
{
private NotLoggedInFaultDetail faultDetail;
public NotLoggedInException( String message )
{
super( message );
}
public NotLoggedInException(
Hi Dan,
i tryed the snap apache-cxf-2.0.3-incubator-20071016.175632-4 to check if
attachments are ok, but there is still some problem...
After tons of testing i finally reproduce thos scenarios (Message send have
2 zip attachments):
Client send and service simply echo the message:
Client
On Thursday 18 October 2007, Benson Margulies wrote:
I was surprised to see that JAXB schematizes the private static final
long serialVersionUID from my exception class. Is there some special
case for these, in spite of being private?
It's probably not JAXB. JAXB cannot handle exceptions
I notice in both scenarios that
Content-Transfer-Encoding: binary
Content-Id: D8E78C856CFEFA300FC2EF5B1B6F05E3
?xml version=1.0 encoding=UTF-8?
lines in the first part (Soap envelope part) are missing... that's wrong?
--
View this message in context:
Got it.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 18, 2007 10:27 AM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB and serialVersionID
On Thursday 18 October 2007, Benson Margulies wrote:
I was surprised to
And the HTTP header content type is wrong
Cencio wrote:
I notice in both scenarios that
Content-Transfer-Encoding: binary
Content-Id: D8E78C856CFEFA300FC2EF5B1B6F05E3
?xml version=1.0 encoding=UTF-8?
lines in the first part (Soap envelope part) are missing... that's wrong?
--
The content type is right in the received SOAPMessage, but for some reason it
changes when it is send back...
Sorry 4 so many mails.. i hope that helps..
I test also with apache-cxf-2.0.3-incubator-20071017.210232-4 with same
results.
/Lorenzo
Cencio wrote:
And the HTTP header content
I think I'm going to need an actual reproducable test case. I've tried
duplicating this here and cannot. It all seems to work OK.
(That is providing the input messages are correct.The logs you sent
definitely had some issues, but that may be due to the mailers or
similar trying to
So you get this message:
Caused by: java.lang.NoClassDefFoundError:
com/sun/el/ExpressionFactoryImpl
at org.jboss.seam.ioc.spring.SpringELResolver.initialize(
SpringELResolver.java:45)
... 149 more
JBoss AS 4.2.1 and 4.0.5 both supply the API class ExpressionFactory in
The NotLoggedInFaultDetail object needs a default constructor. All JAXB
beans need to have a default constructor. If you add that, it should
work.
Dan
On Thursday 18 October 2007, Egor Samarkhanov wrote:
Hi !
I have a simple exception class:
@WebFault(name = faultDetail)
public
Hello !
Thank you, now it works. I think it would be helpful
to provide this info right in the exception.
Thursday, October 18, 2007, 8:06:42 PM, you wrote:
DK The NotLoggedInFaultDetail object needs a default constructor. All JAXB
DK beans need to have a default constructor. If you add
Hi,
right now our in CXF implemented service is throwing the following
exception:
Unmarshalling Error : unexpected element (uri:, local:starttime).
Expected elements are (none)
I checked our code configuration but we couldnt find a bug in it,
right now I think that an
exception occurs, when
CXF does not support RCP/Encoded. Just RPC/Literal.
Dan
On Thursday 18 October 2007, Andreas Bucksteeg wrote:
Hi,
right now our in CXF implemented service is throwing the following
exception:
Unmarshalling Error : unexpected element (uri:, local:starttime).
Expected elements are (none)
?xml version=1.0 encoding=utf-8?
wsdl:definitions
xmlns:s1=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:s=http://www.w3.org/2001/XMLSchema;
One more note:
Judging from the line numbers on the stack trace, you're using version
2.0. 2.0.1 contained a BUNCH of fixes for RPC/Lit. I'd suggest
upgrading to 2.0.2.
Dan
On Thursday 18 October 2007, Daniel Kulp wrote:
CXF does not support RCP/Encoded. Just RPC/Literal.
Dan
package test;
import org.apache.cxf.endpoint.Client;
import org.apache.cxf.endpoint.dynamic.DynamicClientFactory;
import org.streamlinedsalestax.efile.Send;
public class My_EFileService_Client {
public static void main(String[] args) {
My_EFileService_Client driver = new
[Again, Thunderbird threw away my message text. Here is the message
that should have appeared.]
I ran "wsdl2java -all" on the attached wsdl using the apache-cxf-2.0.2-incubator
release.
The generated server driver runs fine.
However, if I write my own server driver using a ServerFactoryBean
[Again. Here is the orginal message.]
ame scenario as my previous post.
I now run the generated server driver
("org.streamlinedsalestax.efile.EFileServiceSoap_EFileServiceSoap_Server").
Runs ok.
I use the attached generic client to get use the service dynamically.
However, I get the
Ant is more than just a development tool, and its code is probably among
the most rigorous and well-tested at Apache. Regardless, if there are
political concerns involved you can rename it cxf-helper.jar or whatever
and it should still work fine.
Glen
Am Donnerstag, den 18.10.2007, 22:37 -0400
It's not just internal - I need to deliver these jars with my application. Just
seems strange to deliver ant.jar with a web service client application.
Lee
-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 18, 2007 7:00 PM
To:
It seems a bit odd to me that DynamicClientFactory (a runtime facility) depends
on ant (a development tool). Is there any plan to remove this dependency?
Thanks,
Lee
Since moving to the latest 2.0.3 snapshot, I'm getting an exception when
marshalling a fault declared on a 'throws' clause. No @WebFault. This
didn't happen with 2.0.2 afaik.
WARNING: Exception occurred while writing fault.
org.apache.cxf.interceptor.Fault: Marshalling Error:
Hi Make sure you have the annotation right. I.e., it needs to be sth like
below:
@Get
@HttpResource(location=/channelName/{id})
public String getChannelName(@WebParam(name = GetBook) GetChannel
getChannel);
If this still does not work, try to play with wrapped and unwrapped style.
eg,
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
Why does it matter which JAR files it internally uses? Code is code.
Glen
Am Donnerstag, den 18.10.2007, 20:42 -0400 schrieb Lee Breisacher:
It seems a bit odd to me that DynamicClientFactory (a runtime facility)
depends on ant (a development tool). Is there any plan to remove this
42 matches
Mail list logo
