The main JAX-WS page should link to
http://cxf.apache.org/docs/a-simple-jax-ws-service.html. I can fix
that. The simple page should be really clear on the role of CXF
extensions (null WSDL, ASM code generation). I'm not entirely clear on
the later.
What do people think of enabling
JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
factory.setDataBinding(new AegisDatabinding());
// perhaps not needed given the endpointInterface annotation
factory.setServiceClass(DocumentDatabase.class);
factory.setAdd
On Monday 11 October 2010 7:55:39 am Benson Margulies wrote:
> What do people think of enabling
>
> JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
> factory.setDataBinding(new AegisDatabinding());
> // perhaps not needed given the endpointInterface annotation
>
On Friday 08 October 2010 10:20:30 am David Valeri wrote:
> Regarding the updates to the OSGi bundle package imports for WSS4J 1.5.9.
> Last I checked (admittedly on the order of a month or two ago), WSS4J 1.6
> has non-backwards compatible changes in it. Is opening the package import
> version ra
We have 6 binging +1 votes and 4 non-binding +1 votes and no other votes.
Thus, this vote passes.I'll get the artifacts promoted.
Thanks!
Dan
On Thursday 07 October 2010 4:44:39 pm Daniel Kulp wrote:
> Once again, there have been a bunch of bug fixes and enhancements that
> have been do
For the record, my +1.
Dan
On Thursday 07 October 2010 5:51:04 pm Daniel Kulp wrote:
> OK.. it staged faster than I expected. :-)
>
> Probably LONG overdue, but I think it's time to finally release CXF 2.3.0!
>
>
> The Maven staging area is at:
> https://repository.apache.org/content
We have 5 binding +1 votes and 3 non-binding +1 votes and no other votes.
THus, this vote passes. I'll promote the artifacts.
Thanks!
Dan
On Friday 08 October 2010 8:32:14 am Alessio Soldano wrote:
> +1
>
> I did some tests with the artifacts in the staging area below (could not
> find t
This would normally belong on user but it's a sort of followup to the
Simple conversation...
I switched my MTOM-ish service to JAX-WS, and now my MTOM items
disappear. My unit tests all fail with null pointers since the data
handlers have nothing in them. It all worked fine with Simple (and
using
Passing an actual 'null' as the first parameter to Service.create
results in an NPF.
On Monday 11 October 2010 8:28:27 am Benson Margulies wrote:
> Passing an actual 'null' as the first parameter to Service.create
> results in an NPF.
That should work. What's the stack trace?
There are a couple of "NoWsdl" tests in:
systests/jaxws/src/test/java/org/apache/cxf/systest/jaxws/Clie
I know a little more about this now
When I used Simple, the effective MTOM threshold was zero. So the data
was always in the InputStream of the data handler.
Well, hmm, with the code below, the data is ending up inline
(presumably because it isn't big enough, or because I somehow failed
belo
On Monday 11 October 2010 8:50:16 am Benson Margulies wrote:
> I know a little more about this now
>
> When I used Simple, the effective MTOM threshold was zero. So the data
> was always in the InputStream of the data handler.
>
> Well, hmm, with the code below, the data is ending up inline
Congrats folks!
--
Craig Tataryn
site: http://www.basementcoders.com/
podcast: http://www.basementcoders.com/?feed=podcast
itunes: http://itunes.apple.com/podcast/the-basement-coders
irc: ThaDon on freenode #basementcoders, ##wicket, #papernapkin
twitter: craiger
On 2010-10-11, at 7:15 AM, Danie
org.apache.cxf.tools.corba.processors.idl.ObjectReferenceVisitor.visitDefaultTypeObjectReference(AST)
is new'ing XmlSchemaType, which should never have been a concrete
type, and isn't one in XML Schema 2.0. What is it trying to do?
On Monday 11 October 2010 11:51:56 am Benson Margulies wrote:
> org.apache.cxf.tools.corba.processors.idl.ObjectReferenceVisitor.visitDefau
> ltTypeObjectReference(AST) is new'ing XmlSchemaType, which should never
> have been a concrete
> type, and isn't one in XML Schema 2.0. What is it trying to
On Monday 11 October 2010 7:48:25 am Benson Margulies wrote:
> The main JAX-WS page should link to
> http://cxf.apache.org/docs/a-simple-jax-ws-service.html. I can fix
> that. The simple page should be really clear on the role of CXF
> extensions (null WSDL, ASM code generation). I'm not entirely c
Re-adding d...@.
On Monday 11 October 2010 9:50:01 am Benson Margulies wrote:
> > Interesting. Not sure how the databinding would have any affect on
> > wether MTOM is enabled or not. The JAX-WS frontend should just be
> > setting the Message.MTOM_ENABLED property on the endpoint and the
>
On Saturday 09 October 2010 9:13:27 am Andreas Veithen wrote:
> On Fri, Oct 8, 2010 at 18:13, Daniel Kulp wrote:
> > And I think this is where the issues may start popping up, but definitely
> > resolvable. If you look at the CXF survey, one of the MAJOR "areas of
> > improvement" for CXF was to
The Apache CXF team is proud to announce the availability of the 2.3.0
release.
Apache CXF is an open source services framework. CXF helps you build and
develop services using frontend programming APIs like JAX-WS and JAX-RS.
These services can speak a variety of protocols such as SOAP, XML/HT
This is what I have so far. Anything to add?
Releases:
DOSGI 1.2 was released
2.2.10 and 2.2.11 patches were released.
The long awaited 2.3.0 release finally occured. Yea!
New committers:
No changes to the PMC or committer list occurred this quarter. This is a
first for CXF.
Communit
On Mon, Oct 11, 2010 at 1:35 PM, Daniel Kulp wrote:
>
> Re-adding d...@.
>
> On Monday 11 October 2010 9:50:01 am Benson Margulies wrote:
>> > Interesting. Not sure how the databinding would have any affect on
>> > wether MTOM is enabled or not. The JAX-WS frontend should just be
>> > settin
On Monday 11 October 2010 4:57:37 pm Benson Margulies wrote:
> On Mon, Oct 11, 2010 at 1:35 PM, Daniel Kulp wrote:
> >
> > At some point in there (would need to debug through), I believe the
> > JAX-WS SoapBinding thing
> > (org/apache/cxf/jaxws/binding/soap/SOAPBindingImpl) sets the property
> >
22 matches
Mail list logo
