:
Looking at src for FaultOutInterceptor.java, BindingOperationInfo op
is null! This only happens for Simple Frontend/Aegis binding, not for
JAX-WS Frontend/JAXB binding.
Is there a way to let it work? I am using cxf-2.0.3.
public FaultInfo getFaultForClass(BindingOperationInfo op, Class
class1
Web Security works for my example A, using JAX-WS Frontend / JAXB binding.
If client sets the wrong password, server will return Security processing
failed. to the client.
Now I want to add WebSecurity to another example B, using Simple Frontend /
Aegis binding.
I use the same
/ReflectionServiceFactoryBean.java
Willem.
yulinxp wrote:
Looking at src for FaultOutInterceptor.java, BindingOperationInfo op is null!
This only happens for Simple Frontend/Aegis binding, not for JAX-WS
Frontend/JAXB binding.
Is there a way to let it work? I am using cxf-2.0.3.
public FaultInfo getFaultForClass
=org.apache.cxf.aegis.databinding.AegisDatabinding
/
/simple:dataBinding
simple:serviceBean
bean class=demo.spring.HelloWorldImpl /
/simple:serviceBean
/simple:server
/beans
--
View this message in context:
http://www.nabble.com/Simple-Front-end-Aegis-binding-server-side-set-up
It's just a directory in the jar files.
On Wed, 2008-01-16 at 10:04 -0800, yulinxp wrote:
where to find classpath:META-INF? Could you pls give me the link?
---
willem.jiang wrote:
They are the spring description files of cxf components.
import
--
View this message in context:
http://www.nabble.com/Simple-Front-end-Aegis-binding-server-side-set-up-problem-tp14841711p14889659.html
Sent from the cxf-user mailing list archive at Nabble.com.
-servlet.xml / this is the
cxf servlet transport component configuration file.
You can find them from the cxf modules class path.
Willem.
--
View this message in context:
http://www.nabble.com/Simple-Front-end-Aegis-binding-server-side-set-up-problem-tp14841711p14890738.html
Sent from the cxf
=demo.spring.HelloWorldImpl /
/simple:serviceBean
/simple:server
/beans
--
View this message in context:
http://www.nabble.com/Simple-Front-end-Aegis-binding-server-side-set-up-problem-tp14841711p14841711.html
Sent from the cxf-user mailing list archive at Nabble.com.
=org.apache.cxf.aegis.databinding.AegisDatabinding /
/simple:dataBinding
simple:serviceBean
bean class=demo.spring.HelloWorldImpl /
/simple:serviceBean
/simple:server
/beans
--
View this message in context:
http://www.nabble.com/Simple-Front-end-Aegis-binding-server-side-set-up
It looks like you're running into the same usage issue as Powel did.
See:
http://mail-archives.apache.org/mod_mbox/incubator-cxf-user/200801.mbox/200801151428.34207.dkulp%40apache.org
Dan
On Tuesday 15 January 2008, yulinxp wrote:
When deploying in tomcat, it's complaining about Caused
They are the spring description files of cxf components.
import resource=classpath:META-INF/cxf/cxf.xml / this is the cxf core
component.
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml / this is
the soap component configuration file.
import
On Thursday 10 January 2008, Nacharya wrote:
We have used the ServerFactoryBean with Aegis databinding and the
exclude annotation didn't work. How can we get this simple annotation
to work?
The @WebMethod(ignore = true) stuff is a jaxws thing. Thus, you would
need to use the
We have used the ServerFactoryBean with Aegis databinding and the exclude
annotation didn't work. How can we get this simple annotation to work?
--
View this message in context:
http://www.nabble.com/exposed-methods-with-Aegis-binding-tp14697814p14743951.html
Sent from the cxf-user mailing
Hi,
Aegis Binding is a data binding , it will not effect which method will
be export to the web service.
If you are using JaxWs front end , you could use the annotation to
define your SEI ( which will be mapped to the WSDL operation)
You can find the example here[1].
[1]https
Basically, you can use the @WebMethod(exclude=true) to exclude the
methods that you don't want it to be exposed.
James
Hi,
Aegis Binding is a data binding , it will not effect which method will
be export to the web service.
If you are using JaxWs front end , you could use the annotation
/
/xsd:sequence
/xsd:complexType
/xsd:schema
However with Aegis binding, the wrapper 'ArrayOf...' elements are
present. xsd:schema attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=http://server.hw.demo/;
xsd:complexType name=ArrayOfString
xsd:sequence
Sounds like a JDK bug or something. I'm not really sure why.
Dan
On Thursday 13 December 2007, tcs wrote:
I set the following system property:
-Djavax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=
com.sun.org.apache.xerces.internal.jaxp.validation.xs.SchemaFactoryImpl
);
svrFactory.setDataBinding(new AegisDatabinding());
svrFactory.create();
--
View this message in context:
http://www.nabble.com/Aegis-Binding---Hello-World-example-fails-with-SchemaFactoryFinder%24ConfigurationError-tp14324396p14324396.html
Sent from the cxf-user mailing list
=getAbcResponse type=tns:getAbcResponse/
xsd:complexType name=getAbcResponse
xsd:sequence
xsd:element maxOccurs=unbounded minOccurs=0 name=return
type=xsd:string/
/xsd:sequence
/xsd:complexType
/xsd:schema
However with Aegis binding, the wrapper 'ArrayOf...' elements are present.
xsd:schema
-question---JDOMException-with-aegis-binding--tf4767403.html#a13667433
Sent from the cxf-user mailing list archive at Nabble.com.
On Wednesday 07 November 2007, BrianP wrote:
Thanks! Got it and it's working. Why is that not on the dependency
list?
What dependency list?
It's in the dependencies for the aegis databinding pom so it should pull
in. It's also shipped in our lib directory and is in the classpath
entry of
this message in context:
http://www.nabble.com/newb-question---JDOMException-with-aegis-binding--tf4767403.html#a13636856
Sent from the cxf-user mailing list archive at Nabble.com.
To: cxf-user@incubator.apache.org
Subject: RE: DefaultTypaMappingRegistry issue [was: Aegis binding and
property/fiels removal]
One additional note: before launching down this path, I strongly
suggest
an experiment in just patching the source of CXF in that method of
XMLTypeCreator to prove
: DefaultTypaMappingRegistry issue [was: Aegis binding and
property/fiels removal]
Benson, Dan,
Could you elaborate a bit on this or detail the steps because I am not
familiar with this. I will then try to test it.
Basically, I have only POGO for which I would like to remove
systematically a property
]
Date: Sep 11, 2007 4:20 PM
Subject: DefaultTypaMappingRegistry issue [was: Aegis binding and
property/fiels removal]
To: cxf-user@incubator.apache.org
Hi Dan,
Sorry not to follow up quickly. Actually, the
DefaultTypaMappingRegistry is final and cannot be extended as you
suggest.
Some more
Message-
From: tog [mailto:[EMAIL PROTECTED]
Sent: Friday, September 21, 2007 4:22 PM
To: cxf-user@incubator.apache.org
Subject: DefaultTypaMappingRegistry issue [was: Aegis binding and
property/fiels removal]
There seems to be an renewed interest for Aegi on the list (thanks
Benson
binding and
property/fiels removal]
Benson,
I have seen a couple of issues related to Aegis binding.
1) If the simple front end POJO has java.lang.Object in it's
signature,
binding fails if you send subclasses of Object in the soap message.
This
is
fairly easy to reproduce and seems
Has anyone looked into this? I'm pretty sure this is a bug which makes it
impossible to use an Aegis binding while using @WebFault. As mentioned in
the original post this is happening because Node.class is not being checked
for in AegisDatabinding.createWriter().
Any ideas?
Zarar Siddiqi
Hi Guillaume
This is a little bit tricky, but doable I think.
Step 1: Write your own TypeCreator which initializes a MyBeanType with your
own BeanTypeInfo. BeanTypeInfos provides metadata about how to map beans to
xml.
public class MyTypeCreator extends DefaultTypeCreator {
@Override
, August 27, 2007 1:23 PM
To: cxf-user@incubator.apache.org
Subject: Re: Aegis binding and property/fiels removal
Hi Guillaume
This is a little bit tricky, but doable I think.
Step 1: Write your own TypeCreator which initializes a MyBeanType with
your
own BeanTypeInfo. BeanTypeInfos
Hi,
I'm getting an UnsupportedOperationException using Aegis binding and JAX-WS
frontend. Here's my setup starting with the Spring beans:
bean id=aegisBean
class=org.apache.cxf.aegis.databinding.AegisDatabinding/
jaxws:endpoint
id=sportsServiceEndpoint
if it defaulted to the class name? It would me more
inline with how XFire rendered the WSDL.
Zarar
Zarar Siddiqi wrote:
I'm using the Aegis binding and all is well except that the Exception
(Fault) is not showing up in the WSDL.
Here's my Spring config.
bean id=aegisBean
class
Below is a snippet of the WSDL that's getting generated using Aegis
binding with the embedded server and causing errors. We're doing Java
first development, no annotations or anything as these are all internal
appsl. When the .NET client tried to connect we were getting a bizarre
error which I
) wrote:
Below is a snippet of the WSDL that's getting generated using Aegis
binding with the embedded server and causing errors. We're doing Java
first development, no annotations or anything as these are all internal
appsl. When the .NET client tried to connect we were getting a bizarre
error
saw this ClassCastException several times in different mailthread
these days.
We need fix it up.
Thanks very much
Freeman
tog wrote:
Hiya
I would like to know if there have been some changes regarding the
Aegis
binding recently (within a month or so) since I now get the following
exception
Hiya
I would like to know if there have been some changes regarding the Aegis
binding recently (within a month or so) since I now get the following
exception:
Thanks
Guillaume
[EMAIL PROTECTED]:~/projects/groovy/cplx_groovyws/client$ groovy Client.groovy
log4j:WARN No appenders could
Hi Tog,
Would you please fill a jira issue and append your test case.
I saw this ClassCastException several times in different mailthread
these days.
We need fix it up.
Thanks very much
Freeman
tog wrote:
Hiya
I would like to know if there have been some changes regarding the Aegis
binding
Anything particularly weird about it? Feel free to create a JIRA issue with
the WSDl and I'll take a look...
- Dan
On 5/9/07, tog [EMAIL PROTECTED] wrote:
I have the small following test:
package com.acme.test;
public class serviceClass {
String sayHello(String name){
return Hello
38 matches
Mail list logo
