Thanks for the added information Ulhas. Willem mentioned that the Celtix context stuff does not work, but that he was looking into to it. Cheers, Eric
> -----Original Message----- > From: Ulhas Bhole [mailto:[EMAIL PROTECTED] > Sent: Friday, November 17, 2006 11:41 AM > To: [email protected] > Subject: RE: JMS WSDL question > > Hi Eric, > > Here is the sample attached of the old client that shows how > it was used. > > I am not sure whether current code supports the same model to > access JMS context info. On other thing to clarify on the > WSDL, configuration, and JMS-context stuff is that JMS WSDL > extensors can be configured via Configuration but some > configuration specific stuff like session pool size cannot be > set in WSDL and same holds true for context info. which > cannot be set via WSDL or configuration. > > Regards, > > Ulhas Bhole > > On Fri, 2006-11-17 at 16:12 +0000, Ulhas Bhole wrote: > > Hi Eric, > > > > It needs to be set programmatically and very few of the > attributes are > > settable. It is set through RequestContext and can be > retrived from > > respose via ResponseContext. > > > > If you want the exact mechanism you will need to search for > some old > > installer of celtix (pre-apache) and look at the JMS samples. > > > > Regards, > > > > Ulhas Bhole > > > > On Fri, 2006-11-17 at 10:30 -0500, Johnson, Eric wrote: > > > No it is a slightly different question. > > > I'm wondering how I go about setting the JMS header > attributes such > > > as JMSPriority. Do I do it in the WSDL using the elements > defined in > > > the jms-context namespace? Is there a way to do this > programmatically? > > > Cheers, > > > Eric > > > > > > > -----Original Message----- > > > > From: Willem Jiang [mailto:[EMAIL PROTECTED] > > > > Sent: Thursday, November 16, 2006 8:40 PM > > > > To: [email protected] > > > > Subject: Re: JMS WSDL question > > > > > > > > Hi Eric, > > > > > > > > I do a quick look into the code, I think current CXF doesn't > > > > support get the header properties from configuration, because > > > > there is no header related beans in the generated code. > > > > I can fill a JIRA task for it and will get it done next week. > > > > One more question, I remember you had a mail for the > JMS Context > > > > Mechanism. > > > > Is it the same question with this header issue? > > > > There are both "Context" related jms-context element and maybe > > > > some kind of Message context :) > > > > > > > > Cheers, > > > > Willem. > > > > > > > > > > > > Johnson, Eric wrote: > > > > > > > > >Willem, > > > > >So I can use the jms-context elements in the WSDL to > specify the > > > > >JMS header properties? Can I also place them in the > configuration file? > > > > >Are there examples? > > > > >Cheers, > > > > >Eric > > > > > > > > > > > > > > > > > > > > > > > > >>-----Original Message----- > > > > >>From: Willem Jiang [mailto:[EMAIL PROTECTED] > > > > >>Sent: Thursday, November 16, 2006 8:07 PM > > > > >>To: [email protected] > > > > >>Subject: Re: JMS WSDL question > > > > >> > > > > >>Hi Eric, > > > > >> > > > > >>You can find the schema of the jms WSDL extensions from > > > > > >>trunk/common/schemas/src/main/resources/schemas/wsdl/jms-context > > > > >>.xsd > > > > >>and > > > > > >>trunk/common/schemas/src/main/resources/schemas/wsdl/jms-conf.xs > > > > >>d > > > > >> > > > > >> > > > > >>Willem. > > > > >> > > > > >>Johnson, Eric wrote: > > > > >> > > > > >> > > > > >> > > > > >>>Can the elements defined in jms-conf and jms-context be > > > > used as WSDL > > > > >>>extensions? For example can I set the session pooling > > > > values or the > > > > >>>time-to-live in the WSDL for a JMS endpoint? > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >> > > > > >> > > > > > > > > > > > > > > > > > > > > > > > >
