Ich werde ab 06.10.2007 nicht im Büro sein. Ich kehre zurück am
22.10.2007.
In dringenden Fällen können Sie sich an Marco Wenger
([EMAIL PROTECTED]) wenden.
Can anyone please help me out on this as I am facing this problem after
migrating to 2.0.2 version.
Thanks,
Durga
gdprao wrote:
>
> Hi,
>
> I am experiencing the following exception after migrating to CXF-2.0.2
> with my REST service which was working fine with CXF-2.0.1 version. If I
> set
Added this to the FAQ:
http://cwiki.apache.org/confluence/display/CXF/FAQ
Dan
On Friday 05 October 2007, Benson Margulies wrote:
> I just answered my own question ... or, to be exact, discovered that
> Dan answered it. I guess that I need some @WebParam's, or to switch to
> contract-first.
>
>
Use the JaxWsProxyFactoryBean instead.The javax.xml.ws.Holder objects
are a JAX-WS thing and thus the interceptors for handling them are part
of the JAX-WS frontend.The ClientProxyFactoryBean is from the simple
frontend that doesn't have all the JAX-WS stuff.
Alternatively, you MAY be
Any chance you could send the Quote.java file?
Also, are you using CXF 2.0.2? There were definite bugs with
collections in 2.0 and 2.0.1.
Dan
On Friday 05 October 2007, Wolf, Chris (IT) wrote:
> I am trying to create a service which returns an array of objects.
> The only success I had wa
The problem is that wsdl2java generates JAX-WS compatible code, but you
are using the simple frontend (instead of the jax-ws frontend) without
specifying the wsdl. (just the service address)
Most likely, you would just need to change the :
new ClientProxyFactoryBean();
to
new JaxWsProxyFactoryB
Hi,
Any update or feedback on this cause it's blocking issue for me?
Thanks in advance,
Hussam Jarada
From: Jarada, Hussam
Sent: Thursday, October 04, 2007 11:58 AM
To: 'cxf-user@incubator.apache.org'
Subject: Invalid namespace with CXF 2.0.2 wsdl2java
Hi,
Hi,
Did anyone know more on this exception or seen this before and know how
to resolve it?
I am using CXF 2.0.2 wsdl2java and ClientProxyFactoryBean ... all
deployed in Apache Tomcat/5.5.23 with JDK 1.5.0_12-b04 in Windows XP
org.apache.cxf.interceptor.Fault: Marshalling Error: class
javax.
It's a difference in namespace. If the @WebService annotation on the
SEI and IMPL have different targetNamespaces (or the package names are
different for the two so they map to different namespaces), the wsdl
gets split with the logical parts (portType) going to the namespace of
the SEI and
Now I realize that it isn't self-referential, it's just a wsdl split up
somehow. Is this somehow a division of labor between the SEI and the
implementation class, and, if so, is there a way to get rid of it?
> -Original Message-
> From: Benson Margulies [mailto:[EMAIL PROTECTED]
> Sent: Fr
I see this coming out of my service, but I can't say that I can easily
believe it.
http://impl.ws.index.rnm.basistech.com/";>
http://localhost:8080/development/NameIndex?wsdl=NameIndex.wsd
l" namespace="http://ws.index.rnm.basistech.com/";>
I will be very interested too, especially for some very good example
implementation.
Regards,
Aurelije
From: Kaleb Walton [mailto:[EMAIL PROTECTED]
Sent: Friday, October 05, 2007 12:41 PM
To: cxf-user@incubator.apache.org
Subject: Re: CXF+ACEGI
I'm yet another person very interested i
I just answered my own question ... or, to be exact, discovered that Dan
answered it. I guess that I need some @WebParam's, or to switch to
contract-first.
https://issues.apache.org/jira/browse/CXF-897
> -Original Message-
> From: Benson Margulies [mailto:[EMAIL PROTECTED]
> Sent: Friday,
I am trying to create a service which returns an array of objects. The
only success I had was returning
List> and using Aegis data binding, but that's not
really what I want. The contrived
example is returning a collection of Quote objects. Quote has two
String fields and a Date field.
I tri
I'm dismayed to find that the WSDL from ?wsdl from my JAX-WS service has
parameters named 'arg0, arg1, ...' instead of the names derived from
reflection into the method parameter lists. Is this to be expected?
I'm yet another person very interested in securing my services using Acegi
as we will be using it as our primary method of authentication over all of
our service transport mechanisms (RMI, HTTP, etc.).
If someone has a soup-to-nuts example implementation that would be great to
see!
Regards,
Kale
@Transactional annotation did not help either. I guess Facade solution might
be the only solution for now ...
Thanks,
On 10/5/07, Willem2 <[EMAIL PROTECTED]> wrote:
>
>
> Yes , the key is we can't inject the WebContext resource into implementor
> which is enhanced by Spring AOP.
>
> Can try you
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, 2007 9:48 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: jaxws:endpoint versus interface versus servic
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
>
>
>
--
Apparently not understanding the rules of JAX-WS, I constructed a web
service with the following shape: all the annotations were on the
interface, none were on the implementation. I thought that this code
would cause the JAX-WS runtime to pull annotations off of the interface
and invoke the impleme
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
Here is concrete evidence of the Log4jConfigListener having disasterous
effects on CXF.
The variable is the comments in the following web.xml fragment.
org.springframework.web.context.ContextLoaderListener
With org.springframework.web.util.Log4jConfigListener:
jetty.run:
Hi all,
Is there any way to configure layout (ordering) of security items in
security header using WSS4J? or that's specific to WSS4J implementation?
My question is specific to using WSS4J and spring configuration in CXF.
With Regards,
Mayank
Yes , the key is we can't inject the WebContext resource into implementor
which is enhanced by Spring AOP.
Can try you add the transaction annotation to setWsContext method?
And there is an another way to walk around it just by adding a facade which
do not use any Spring AOP stuff and wraps th
You can try to run my test case ResourceInjectorTest[1] with mvn test
-Dtest=ResourceInjectorTest in the trunk\common\common\ directory.
I do not thing this NPE is caused by jdk1.6.
[1]
https://svn.apache.org/repos/asf/incubator/cxf/trunk/common/common/src/test/java/org/apache/cxf/common/injection
Willem,
I tested by removing , and worked well. I got the
WebServiceContext. But when I put it back I got null again.
On 10/5/07, Mustafa Egilmezbilek <[EMAIL PROTECTED]> wrote:
>
> :(
>
> Still null pointer exception
>
> You said your tests were successful. Which jdk are you using. Do you think
:(
Still null 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
Hi all.
I have a web service and I need to know what user name call each time to my
web service.
In my service implementation I have a declared:
@javax.annotation.Resource
private WebServiceContext context;
With this variable I can access to MessageContext and
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) in the method to
exclude it from the wsdl operation.
Sprint Dynamical Proxy is based on the interface, so we nee
Thanks, I check it and WebServiceContext is not null I was mistaken, but the
RECV_RESULTS from the MessageContext it´s null, now that is my problem.
I will fix in a new post now.
blacksheep wrote:
>
> Hi,
>
> If you are using Spring AOP in your project, the WebServiceContext returns
> null.
Hi,
If you are using Spring AOP in your project, the WebServiceContext returns
null.
Thanks to Willem (from Iona), he put a fix (issue CXF-1074) and checked it
in the trunk. The fix failed in my case but might work for your case. Please
get the latest trunk and build and use it. (
http://incubato
Problem solved. In my development environment I was using the port number
(so without using Apache) but to call the web service in the test
environment I omitted the port number and the URL was decoded two times.
So now I only need to understand how to avoid this behaviour also when the
port is no
Hi all.
I need to know how get the user name that is invoking a web service. I have
a WebServiceContext in my webservice implementor class, WebServiceContext
has a method "getUserPrincipal", but WebServiceContext is null and i cant
acces to it. I read how to write a custom Interceptor but i dont
Willem I got the latest trunk and the got rid of the:
java.lang.IllegalArgumentException: object is not an instance of declaring
class ... exception.
But WsbServiceContext is still null :(
On 10/5/07, Mustafa Egilmezbilek <[EMAIL PROTECTED]> wrote:
>
> When did you commit your code ? I started to
34 matches
Mail list logo
