Andrew,
It's quite possibly a bug. While working on the WSPolicy annotations last
month, I discovered a BUNCH of places in ServiceWSDLBuilder (the class that
builds WSDL's from the service model) that were not calling the
addExtensibilityElements to add the extensors or calling addDocumentation to
add the documentation elements. It's quite probable that they aren't calling
the addExtensibilityAttributes method in all the needed places either.
Check in there for the place where the portTypes are created and see what it's
doing. Log a bug with a patch if I'm right. ;-)
Dan
On Mon September 21 2009 8:30:19 am Andrew Harrison wrote:
> Hi,
>
> A while back I threatened to implement WS-Eventing in CXF. I roughed
> it in, but I have time to do it properly now.
> So one thing I've noticed - I can't seem to set a WSDL portType
> attribute from an InterfaceInfo object. I've tried:
>
> info.addExtensionAttribute(new QName("http://www.w3.org/2009/06/ws-
> evt", "EventSource"), "true");
>
> but this doesn't get queried in
> org.apache.cxf.wsdl11.ServiceWSDLBuilder so doesn't appear in the WSDL.
> Going from WSDL to an InterfaceInfo object works fine.
>
> I'm working off the svn code.
>
> cheers,
>
> Andrew
>
> On 24 Mar 2009, at 22:06, Andrew Harrison wrote:
> >>> I'm
> >>> implementing WS-Eventing.
> >>
> >> oooooo....... Is the WS-Eventing stuff you are working on
> >> possibly a
> >> candidate to submit to CXF? :-)
> >>
> >> Dan
> >
> > Sure. I'm actually hacking this together in a matter of days at the
> > moment, so it's not very pretty at the moment. But I was hoping to
> > revisit it in a few weeks and see what could be salvaged.
> >
> > cheers,
> >
> > Andrew
>
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
