On Monday 08 November 2010 6:54:45 pm firasarabo wrote:
> HI Daniel,
>
> all cxf jars are still in the WEB-INF/lib/ direcotry of the war file, I
> also tried to have them in the external direcotry however doing that
> caused more issues than I needed. so I put them in both places, the
> external d
Does you configuration work with 2.0.x?
Can provides a simple test case to reproduce the error ?
On 10/28/10 8:42 AM, Leamon, Pat wrote:
Hi,
I'm trying to upgrade from 2.0.x to 2.2.10/2.2.11 and have hit a
strange issue. It seems to boil down to my
definitions being ignored when validatin
>> Do you know what the expected release date of 2.3.1 is? Whats the
>> normal dev cycle?
>
> I'm thinking the end of Nov or first week in Dec. Normally, it's about every
> 8 weeks. However, with 2.3.0 being a ".0", I'm likely to shorten it a couple
> weeks just to get the ".1" out there. I'
Can I have a look at the configuration of your cxf-extension-interact.xml?
BTW, can you make sure your customer jar is wrapped into the war rightly?
--
View this message in context:
http://cxf.547215.n5.nabble.com/org-apache-cxf-BusException-No-DestinationFactory-was-found-tp3252224p3256068.html
HI Daniel,
all cxf jars are still in the WEB-INF/lib/ direcotry of the war file, I also
tried to have them in the external direcotry however doing that caused more
issues than I needed. so I put them in both places, the external dirctory
and WEB-INF/lib directory, may be having them in two pacese
On Friday 05 November 2010 7:51:19 pm Yonghe wrote:
> Hi,
>
> I am trying to create a WS-Trust client for .net 4.0. However, CXF's
> wsdl2java reports stack overflow while parsing the wsdl from .net's
> SecurityTokenService.
What version of CXF? 2.3.0 seems to not stack trace, but doesn't actua
On Monday 08 November 2010 7:50:10 am Jason Pell wrote:
> Hi,
>
> The changes look good - Arrays no problem. I will wait for the maven
> snapshot to come down and clean up my code. I don't use
> SimplePrincipal myself. The Spring Framework
> UsernamePasswordAuthenticationToken class implements
On Friday 05 November 2010 12:57:56 pm KARR, DAVID (ATTSI) wrote:
> I've concluded that writing a custom logging interceptor requires
> writing it from scratch, as opposed to trying to use the
> Logging{Out,In}Interceptor as a base class or assuming it was executed
> previously in the chain. I've
On Friday 05 November 2010 1:56:49 pm Bayu Anggorojati wrote:
> Hi Dan,
>
> Thank you for your highlight. I checked the applicationContext.xml, and
> there is these lines of codes for configuring CXF web service:
>
> implementor="#queryOperationsWebService" address="/" />
> implementor="#que
On Monday 08 November 2010 11:56:50 am firasarabo wrote:
> Hi,
>
> all the necessary files are in the META-INF/cxf folder, that is why the
> project works fine if I put the interact jar file in WEB-INF/lib directory
> of the war file. the project gives the error I have posted only if I put
> the j
With 2.3.0 (likely for 2.2.11 as well), we added a parameter to the
createClient methods on the DynamicClient to specify binding files to pass to
jaxb.There is a jaxb binding customization to have it set the generated
beans as serializable which would be applicable to this.
Dan
On Sunday
On Monday 08 November 2010 6:55:08 am almo wrote:
> IU have the same problem, did you find how to solve it??
If using a custom spring context instead of a default Bus, you likely need to
import:
META-INF/cxf/cxf-extension-policy.xml
META-INF/cxf/cxf-extension-ws-security.xml
META-INF/cxf/cxf-ex
On Monday 08 November 2010 7:33:14 am lweil wrote:
> Hi,
>
> We are providing a set of services that are used by multiple clients,
> including a .net call center app.
>
> This app seems to make a call to our service firstly to get the WSDL,
> turning on debugging on our servers we see the followi
On Monday 08 November 2010 1:30:14 pm Robert Liguori wrote:
> Metro includes a package in jaxws-rt.jar that allows for dumping of SOAP
> traffic without HTTP headers. Reference: *Java Web Services Up and
> Running*, page 15.
>
> Does CXF provide this same or a similar feature... if so, how?
I don
This is how JAXB outputs things by default. It pretty much always outputs
all the namespaces that it knows about at the "root" of the document that it
is writing.
You can control it somewhat by createing a
com.sun.xml.bind.marshaller.NamespacePrefixMapper and registering that with
the JAX
I am trying to generate a ws-trust client. However, wsdl2java reports stack
overflow while parsing the wsdl from SecurityTokenService server. Here is
the wsdl: http://cxf.547215.n5.nabble.com/file/n3255535/sts.zip sts.zip . I
also used Metro's wsimport to parse the wsdl and it is fine. seems to m
On Monday 08 November 2010 3:46:03 am Jason Pell wrote:
> Hi,
> I am using a project which relies on 2.2.3 and I noticed jax ws frontend
> 2.3.1 relies on 3.3. I excluded 3.3 and set a dependency on 2.2.3 and all
> seemed to keep functioning.
>
> What are potential repurcussions of excluding 3.3
Metro includes a package in jaxws-rt.jar that allows for dumping of SOAP
traffic without HTTP headers. Reference: *Java Web Services Up and Running*,
page 15.
Does CXF provide this same or a similar feature... if so, how?
Thanks!
On Saturday 06 November 2010 4:52:07 pm Robert Liguori wrote:
> And the best defined usages for Apache CXF tooling goes to:
>
> 1) Command line help for each tool
In general, this is the "cannonical" list of options. In CXF, the help for
this is generated directly from the XML file that also d
On Sunday 07 November 2010 3:37:42 pm Kent Närling wrote:
> OK, thanks, Daniel, to the point as always! :-)
>
> A followup question:
>
> I HAVE looked in the WSDL already (we use SoapUI for testing, hard to
> avoid seeing the mapping ;-) ) and the data seems to be represented in
> a very straight
Tosh,
Were you able to get an answer to your question about getting the SOAPAction
header populated? I am having this issue while trying to connect to a .NET
Web Service as well.
Thanks,
Nels
--
View this message in context:
http://cxf.547215.n5.nabble.com/HTTP-SOAP-Action-Header-blank-tp32047
Hi,
all the necessary files are in the META-INF/cxf folder, that is why the
project works fine if I put the interact jar file in WEB-INF/lib directory
of the war file. the project gives the error I have posted only if I put the
jar file in an external folder outside of the war file.
so the issue
Hi,
We are providing a set of services that are used by multiple clients,
including a .net call center app.
This app seems to make a call to our service firstly to get the WSDL,
turning on debugging on our servers we see the following message passed in
on this call:
http://www.w3.org/2003/05/s
IU have the same problem, did you find how to solve it??
--
View this message in context:
http://cxf.547215.n5.nabble.com/Using-WS-Policy-with-CXF-tp552435p3254943.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi,
The changes look good - Arrays no problem. I will wait for the maven
snapshot to come down and clean up my code. I don't use
SimplePrincipal myself. The Spring Framework
UsernamePasswordAuthenticationToken class implements principal and I
am using spring security for authentication so I jus
Hi
On Fri, Nov 5, 2010 at 9:48 PM, Jason Pell wrote:
> Hi,
>
> ...
> Also while I have your attention. I was confused as to why the
> changes to WSS4JInInterceptor for ws-security.ut.no-callbacks do not
> support direct configuration of the interceptor (I noted this perhaps
> incorrectly on the
Hi Jason
thanks for experimenting with the new code, there's a chance some signatures
and even packages might change before 2.3.1 as it is still a work in
progress but hopefully we won't do many more changes...
See more comments inline...
On Fri, Nov 5, 2010 at 10:58 PM, Jason Pell wrote:
> Hi
Hi,
Did you already follow Sergey's suggestion, I believe he is correct,
in your custom transport project, you need more files in src/main/
resources/META-INF/cxf folder, I believe you already have cxf-
extension-interact.xml in this folder, please check if you also have
files like bus-ex
Hi,
I am using a project which relies on 2.2.3 and I noticed jax ws frontend 2.3.1
relies on 3.3. I excluded 3.3 and set a dependency on 2.2.3 and all seemed to
keep functioning.
What are potential repurcussions of excluding 3.3
Sent from my iPhone
Hi,
Yes, the jar file is in the class path. a quick test I did is removing the
jar file from the class path and I get the error of not able to find
"META-INF/cxf/cxf-extension-interact.xml" which is in the jar file, I put
the jar file back in the class path and the error is gone. so the jar file
30 matches
Mail list logo
