Are you sure the server isn't responding with http 503?
On 9/24/07, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> This error has really killed me since I thought this error was a SoapFault
> coming back from a 3rd party companies webservice when in fact it appears
> like CXF doesn't always properly ha
If you search back you'll see I worked through some similar
discussions in this area...
I wanted to write one endpoint that could handle SOAP, POX and REST.
With some help I was able to get the SOAP and POX stuff working great,
REST however never seemed to set the properties, I haven't spent much
has a complete ACEGI security solution and posts
> >> it
> >> it will be Awesome! Ray do you mind posting a complete sample. It will be
> >> greatly beneficial to everybody.
> >>
> >> Matt
> >>
> >>
> >> dkulp wrote:
> >
Another factor in the discussion has to do with what you want to
secure. Acegi is built to secure web applications. It does this by
providing various ways to secure the HTTP communication.
The authorization and authentication concerns are addressed at the
protocol layer first, and can then be exte
Is there any sort of roadmap in place for when CXF is expected to be
voted out of the incubator?
Acegi can be used on the secure the application the server-side.
WS-Security stuff can be used as well.
Your client side application need only present the credentials to the
server to say who it wants to log in as. That's not a an Acegi thing,
it's really not even a java thing at that point.
If y
You want the client to tell the server how to do security? That sounds crazy :)
Your client side should either be doing http based security or
ws-security. That doesn't have anything to do with Acegi at that
point.
On 9/14/07, Zarar Siddiqi <[EMAIL PROTECTED]> wrote:
>
> I'm trying to understand
pain. One big jar is easy to put in, lots of
little ones takes an aggravatingly long time...
Not a big deal, and definitely not a deal breaker for me using CXF at
this point :)
On 8/29/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> On Wednesday 29 August 2007, Ray Krueger wrote:
&g
release, under "lib" directory.
> For example, for CXF 2.0 release, the file is lib/cxf-2.0-incubator.jar
>
> Cheers,
> Bo
>
> Ray Krueger wrote:
> > Are there any plans to have a single cxf-version.jar distribution?
> > There are just too many modules to figure o
Are there any plans to have a single cxf-version.jar distribution?
There are just too many modules to figure out. I'm lazy and I don't
really care how big the jar is. Spring is available in modular jars,
or as one big spring-version.jar; any chance CXF would do something
similar?
try to retrieve the wsdl with the name
> "username=TEST&password=password" , then a NPE will be thrown when
> WSDLQuery can't find the wsdl definition .
>
> If you want to protect your wsdl, I think you can write your custom
> WSDLQueryHandler and add it to the Query
This might seem like an odd answer, but you can also look at how
Spring-WS does it...
http://static.springframework.org/spring-ws/site/reference/html/security.html
On 8/27/07, Kaleb Walton <[EMAIL PROTECTED]> wrote:
>
>
> Does anyone have an example of authenticating with Acegi Security using a
>
I opened bug CXF-948 for this, but anyway; here's the problem.
Deploying CXF via the CXFServlet, you will get a NullPointerException
when your URL contains extra parameters...
This URL
http://localhost:8181/ws/soap/CurrencyExchange?wsdl&username=TEST&password=password
Causes this stack trace...
You can do it with Groovy 1.1
http://groovy.codehaus.org/Annotations+with+Groovy
On 8/21/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> Kaleb,
>
> The jaxws stuff would require the service implementor to have the
> @WebService annotation. A script obviously wouldn't have that.
>
>
> Couple thin
eService" />
>
> Where test.SomeServiceImpl implements DisposableBean
>
> Thanks again.
>
>
> Ray Krueger wrote:
> > Spring is used behind the scenes for everything in CXF though. You
> > should be able to implement those. Again, if you're willing t
> I am using the CXFServlet to load the endpoints, so the spring
> interfaces do not work. Is there a CXF way to do this?
>
> Ray Krueger wrote:
> > You can probably implement Spring's InitializingBean and
> > DisposableBean interfaces. Those are called d
You can probably implement Spring's InitializingBean and
DisposableBean interfaces. Those are called during the BeanFactory
lifecycle.
http://www.springframework.org/docs/api/org/springframework/beans/factory/InitializingBean.html
http://www.springframework.org/docs/api/org/springframework/beans/fa
> >
> >
> >
> >
> >
> >
> > beans removed
> >
> >
> >
> >
> >
> >
> > On 8/16/07, Dan Diephouse <[EMAIL PROTECTED]> wrote:
> > > What does your servlet/web.xml c
ng it with Spring & the ContextLoaderListener, you need to
> import the cxf config files inside your cxf.xml:
>
>
>
>
>
>
> - Dan
>
> On 8/15/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> >
> > Does anyone have a clue why the
&g
Does anyone have a clue why the
bus.getExtension(ResourceManager.class) would return null?
The mere existence of a cxf.xml in my app causes the NPE I mentioned below.
On 8/14/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> If I add the following cxf.xml file (from he wiki) to my buil
If I add the following cxf.xml file (from he wiki) to my build I get a
NullPointerException from the CxfServlet. It seems that the
bus.getExtension(ResourceManager.class) is returning null. I am using
cxf-2.0.1-incubator.
((cxf.xml))
http://www.springframework.org/schema/beans";
xmlns:xsi=
I didn't get a chance to comment again earlier...
Yes, adding the soapbinding fixed up the bad xml. But message names
and part names are all wrong still. They are just continuations of my
operation name. The @WebParam annotation properties seem to be
ignored.
On 8/9/07, James Mao <[EMAIL PROTECT
I am working from the following interface...
@WebService(targetNamespace = CurrencyExchangeNamespace.URI, name =
"CurrencyExchange")
public interface CurrencyExchange {
@WebResult(targetNamespace = CurrencyExchangeNamespace.URI,
name = "ExchangeResponse", partName = "ExchangeRespo
war to a
> directory is all that is required to deploy to a container) which in my case
> would support jboss.
>
> - Erlend Leganger
>
> On 03/08/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> >
> > The CXF crew should look at making the samples deploy in a more
> >
The CXF crew should look at making the samples deploy in a more
standard fashion.
Currently the deployment requires man-handling all of the cxf jars
into Tomcat's classpath, rather than packaging them into a WAR.
Building a WAR would give us the ability to try out the samples in our
container of
Nevermind, I saw the way on the wsdl-to-java wiki page where it talks
about specifiying a jaxws binding file...
${basedir}/src/main/schema/fx/CurrencyExchange.wsdl
-verbose
On 8/2/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> Is there a way to pass the -verbose
I opened https://issues.apache.org/jira/browse/CXF-875 for this issue...
Basically if I use the xformat namespace extension in my bindings the
wsdl2java tool throws an NPE because it tries to lookup a null
transport URI in the DestinationFactoryManager.
Is there a way to pass the -verbose argument through to the plugin?
I see some "extraargs" property on the WsdlOption class, but I cannot
figure out how to set it from my pom.
If your're using IDEA you can register an XSD resource to use when it
sees that URL, rather than having it try to use the literal one.
If you're using Eclipse, well, I guess you should be happy if you have
syntax highlighting...
Ok ok, that was uncalled for.
Seriously, for eclipse it depends on t
;;>
http://cxf.apache.org/bindings/xformat";>
On 7/31/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> wow James that's fantastic, thanks!
> I'll give this a shot this morning (CST) and let you know how it goes.
>
> On 7/30/07, James Mao <[EMAIL PROTECTED]>
es, you have to specify the @WebService and also @BindingType
> > determine the binding you are using
> > in case of SOAP1.1 you can omit the annotation, but you have to
> > specify the @BindingType for the XML binding and for the SOAP1.2 binding
> >
> > But it's also
OK, I see now that the trick to getting what I want to work involves
using the xformat:binding element in my wsdl:bindings.
Does this mean that I can't support both POX and SOAP using the same
@WebService impl?
On 7/30/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> Was just playi
Was just playing around with the hello_world_xml_bare, the
functionality is about what I want. But I'd like to be able to run it
in the servlet container, not using that Endpoint.publish stuff.
I have a working jaxws endpoint, I would like CXF to handle an
incoming xml POST, unmarshall the payload
Sorry...
More specifically, I'd lile to use the Impl, Request, and Response
classes that the wsdl2java toll generated.
On 7/30/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> Yes, that is exactly what I mean.
> Though I'd rather not deal with the payload directly. I'd l
e.org/CXF20DOC/rest-with-jax-ws-provider-and-dispatch.html
>
>
>
> Cheers,
> Jervis
>
> -Original Message-
> From: Ray Krueger [mailto:[EMAIL PROTECTED]
> Sent: 2007?7?30? 19:26
> To: cxf-user@incubator.apache.org
> Subject: Plain Old Xml over Http
>
>
> I'
I'm loving CXF right now by the way, so thanks for that :)
I'd like to be able to send my current WSDL types over the wire
without soap envelopes as plain-old-xml via http POST operations.
I started with a WSDL and a pair of Request/Response type objects...
Running wsdl2java generates a perfectl
36 matches
Mail list logo
