Sorry about this question; just realized it's purely JAXB-related.
I've gotten around it by using @XmlSeeAlso as follows:
@XmlRootElement(name = "resultsPage")
@XmlSeeAlso({ ArticleInfo.class })
public class ArticlePage extends ResultsPage {
}
On Tue, 26 Apr 2011 16:23:
Hello,
I am using CXF 2.4.0 + Spring 3.0.5 to create JAX-RS services. In one case
I have a service for which I need to marshal a generic type. When I go
about doing this, I end up getting an exception like this:
[javax.xml.bind.JAXBException: class my.package.ArticleInfo nor any of its
su
Hello,
I'm trying to configure CXF to use log4j. I've created
META-INF/cxf/org.apache.cxf.logger and added a log4j.properties. Indeed
CXF uses log4j for almost everything except a cases. Specifically, the
methods that seem to ignore this configuration are:
org.apache.cxf.service.factory.Refl
Hi,
When CXF loads, from what I understand, it scas that classpath for
extensions. Is there a way to control extension loading?
The reason I want to do this is because I want to use CXF 2.2.6 in the
Geronimo 2.2 app server. Geronimo already includes CXF 2.1.4. Therefore,
in a geronimo-specif
With JAX-WS, I think you can set a flag "header=true" in the web service
interface. Like:
public void someWebMethod(@WebParam(header=true) String myHeaderParam);
The targetNamespace/name can be added to the annotation to specify these
aspects.
In fact, if you start from WSDL, I'm pretty sure
Benson Margulies wrote:
I've got a webapp with a CXF service. When I'm doing development, I'm
fine with the usual default wsdlLocation. However, when I deploy,
there's a firewall.
Customizing the Spring app context and rebuilding the webapp is not an
attractive prospect. Has anyone come up with
etSOAPBody();
//check the content of body and return null if RM.
}
return super.getString(key, mc);
Dan
On Fri December 11 2009 10:58:10 am Alexandros Karypidis wrote:
Hi,
SHORT STORY:
I need to encrypt an element in my SOAP message. Therefore I configure
my sending endpoint as foll
Hi,
SHORT STORY:
I need to encrypt an element in my SOAP message. Therefore I configure
my sending endpoint as follows:
This generally works, but breaks if I enable WS-ReliableMessaging (with
a policy in the WSDL). In that case, when trying to send a message the
interceptor fails with:
Hi,
I intend to use JAX-WS to access web services from within servlets in a
clustered environment.
Rather than create a proxy for each servlet invocation, I'd like to
cache the client stub in the session object.
Does CXF use serializable objects when creating JAX-WS proxies? Is it
safe to
I think I have an idea why it is trying to search the JBoss bin folder.
Most likely it's the "current working directory" and your WSDL
references the xsd without specifying an absolute/relative path. If you
change the import in the WSDL to something like
"DOES_IT_MAKE_SENSE/packaging.valueobjec
really shouldn't be null
at this point as far as I can tell.
Dan
On Mon November 30 2009 2:09:01 pm Alexandros Karypidis wrote:
Ok, I've been reading through the source code of CXF and found that the
error seems to be related with the service mode and the SAAJ
interceptor.
age.put("write.attachments", Boolean.TRUE);
}
}
message.getInterceptorChain().add(internal);
} // === end of addition
}
Does this sound right?
Alexandros Karypidis wrote:
Hi,
I need some help with WS-Policy in CXF 2.2.4
I have been fighting to enable WS-Addressing using the WS-Addressing
Metadata po
Hi,
I need some help with WS-Policy in CXF 2.2.4
I have been fighting to enable WS-Addressing using the WS-Addressing
Metadata policy assertions. I attahed a policy in my WSDL with:
xmlns:wsp='http://www.w3.org/ns/ws-policy'>
xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'
FIY I also needed to implement this and have nearly got it working.
The key to cracking the solution was to:
1. Use @WebServiceProvider to implement the receiving endpoint -- the
JAXB bindings won't work if the message is not processed (especially if
encryption is used), so you'll need to work
Firtly, thank you for your reply.
Your e-mail pointed me to the relevant code (ReadHeadersInterceptor
specifically). I ended up reading CXF code and found that the headers
check is performed by the SOAP binding module and specifically the
MustUnderstandInterceptor.
To make the long story sho
Hi,
I have a CXF endpoint that uses @WebServiceProvider to process the SOAP XML.
The sender uses WS-Security so the message includes in its SOAP header:
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
soap:mustUnderstand="1">
This causes CXF to
Hi,
I have a test that initializes a cxf bus, and then goes on to create a
JAX-WS service + client and enable WS-RM using the "features" API.
However, the server side seems to no have "WS-Addressing" and "WS-RM"
enabled. The code looks like:
JaxWsServerFactoryBean factory = new JaxWsServerFa
that I'd read that you are sticking with some other JAX-RS platform.
Is the
CXF JAX-RS stuff in there? I use at least one CXF-specific bit of REST.
On Wed, Nov 4, 2009 at 4:05 AM, Alessio Soldano
wrote:
Alexandros Karypidis wrote:
So I did a quick test with JBoss 5.1 using the Native core
1.6.0_04, you mileage will vary.
Alexandros Karypidis wrote:
You might want to consider writing a couple of maven profiles and
distribute two packages. For example have a look at how Liferay
distributes several different bundles:
http://sourceforge.net/projects/lportal/files/Liferay%20Portal/5.2.3
practical.
--benson
On Tue, Nov 3, 2009 at 8:56 AM, Alexandros Karypidis wrote:
Benson Margulies wrote:
I've got a working webapp with CXF in it, and I must now deploy it on
JBoss.
Does someone have a recipe for dealing with whatever problems with
endorsed
jars and such are li
Benson Margulies wrote:
I've got a working webapp with CXF in it, and I must now deploy it on JBoss.
Does someone have a recipe for dealing with whatever problems with endorsed
jars and such are likely to come up?
Hi,
I'm also using CXF extensively with JBoss and I've found that the best
wa
endpoint; currently it is not possible to have that endpoint
published by JBoss.
Alexandros Karypidis wrote:
Thank you Daniel, it works as advertized.
One extra note to anybody using JBoss to do this: You will need to
manually add the Jetty to JBoss' CXF integration deployer as discussed
i
messages.You can do it via API's as
well. See:
http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html
Dan
On Wed October 21 2009 2:14:58 am Alexandros Karypidis wrote:
Hi,
What is the CXF API/configuration that allows me to set the EPR value
for Reply
"http://localhost:/myAddress";); <== THIS DOES NOT WORK
Alexandros Karypidis wrote:
Hi,
What is the CXF API/configuration that allows me to set the EPR value
for ReplyTo/FaultTo in WS-RM?
My problem is that the client always connects to the web service
provider using an "anonymous
Hi,
What is the CXF API/configuration that allows me to set the EPR value
for ReplyTo/FaultTo in WS-RM?
My problem is that the client always connects to the web service
provider using an "anonymous" endpoint reference. I would like to change
that so that the client's EPR is specific and pers
Hello,
It would be beneficial if you'd post the error (Exception) you're
getting and the way you've configured your service. I've just recently
managed to get a WS-RM service running, although I'm using CXF on both
sides (WebLogic and JBoss).
Anyway, there are various ways to configure WS-RM
rsion of CXF? If you aren't using 2.2.4, I'd suggest trying that.
With 2.2.x, there is no need to do:
as the engine defaults to on.
Dan
On Mon October 19 2009 9:38:59 am Alexandros Karypidis wrote:
Hi all,
I'm trying to publish a WS-RM service on WebLogic 10.3.1
Hi all,
I'm trying to publish a WS-RM service on WebLogic 10.3.1. I am using the
JAX-WS frontend and CXFServlet. When I enable WS-RM, I get a
NullPointerException (see stack trace at end of message) regarding the
WS-Policy. I define the policy in the WSDL and enabling the policies
features in
28 matches
Mail list logo
