WSDL's and extensors....

[Daniel Kulp <da...@iona.com>]

Ran into a slight snag....

Several of the more advanced things in Celtix are defined/activated based 
on extension elements in the WSDL.   In celtix, those extensors are 
defined by a schema and code generated using JAXB.   We register an 
ExtensionRegistry with the WSDLReader so the extensors get parsed into 
the correct concrete types.

However, there doesn't seem to be a way to add an ExtensionRegistry into 
SCDLAssemblyModelLoader.   Thus, none of our extensors are coming out as 
the expected concrete type.

Anyway, there was a mention on the chat today about the wsdl import stuff.   
Is this something that is known and being addressed?

Thanks!
-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727  C: 508-380-7194
daniel.kulp@iona.com

Re: WSDL's and extensors....

[Daniel Kulp <da...@iona.com>]

Talked to Jeremy on the IRC (isn't IRC nice for resolving these issues) 
and we've come up with a plan to add an ExtensionRegistry to the 
WSDLDefinitionRegistry that can be used to solve this problem.   Celtix 
can use and anyone else that needs it can also use it.

Thanks!
Dan

On Monday 17 April 2006 14:11, Daniel Kulp wrote:
> Ran into a slight snag....
>
> Several of the more advanced things in Celtix are defined/activated
> based on extension elements in the WSDL.   In celtix, those extensors
> are defined by a schema and code generated using JAXB.   We register an
> ExtensionRegistry with the WSDLReader so the extensors get parsed into
> the correct concrete types.
>
> However, there doesn't seem to be a way to add an ExtensionRegistry
> into SCDLAssemblyModelLoader.   Thus, none of our extensors are coming
> out as the expected concrete type.
>
> Anyway, there was a mention on the chat today about the wsdl import
> stuff. Is this something that is known and being addressed?
>
> Thanks!

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727  C: 508-380-7194
daniel.kulp@iona.com