cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhole, Ulhas" <>
Subject RE: JMS address wsdl extension
Date Mon, 12 Feb 2007 11:46:31 GMT
Hi James,

Can you be more specific on which schemas you are referring to? 

DestinationStyle is in JMSAddressPolicyType.
UseMessageIDAsCorrelationID & DurableSubscriberName are in

jndiProviderURL and initialContextFactory is missing which should have
been into JMSAddressPolicyType. I just had a look at the code in
JMSProviderHub which calls onto the JMSUtils.getInitialContext()and it
looks like these properties are no longer taken from the WSDL extensor
directly as attributes but come from the name-value pairs properties in
the WSDL Extensor. 

I did the initial work with JMS in celtix land but don't know all the
changes that happened in CXF so may be missing something but my feeling
is the changes must have been made to generalize the mechanism of
getting connection to work with differences in getting connection
brokers address via generic properties that goes into environment for
getting initialContext.


Ulhas Bhole

-----Original Message-----
From: James Mao [] 
Sent: 12 February 2007 02:13
Subject: JMS address wsdl extension


I'm working on porting wsdl2service from tools to tools2, i have reused
the wsdldefinition builder in the rt.
But i found that the jms extension schema is not consist with the one in

Several address extensions are lost. e.g DestinationStyle
jndiProviderURL initialContextFactory UseMessageIDAsCorrelationID

I'm not jms expert, so i would like ask our jms guru, if those
attributes are needed any more?

BTW, the namespace in jms.xsd is,
and we use the jms.xjb to change the namespace to

Is it necessary?  why not use 
directly in jms.xsd?


View raw message