Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of Eric.Johnson@iona.com
 designates 65.223.216.181 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: JMS WSDL question
Date: Fri, 17 Nov 2006 11:48:03 -0500
Message-ID: <8DA58330BA060E41AB52B73294034EA6149042@amer-ems1.IONAGLOBAL.COM>
Thread-Topic: JMS WSDL question
Thread-Index: AccKZsFqYzqd+lmLQoS4w39l6Q4GSwAARtdw
From: "Johnson, Eric" <Eric.Johnson@iona.com>
To: <cxf-dev@incubator.apache.org>, "Bhole, Ulhas" <ulhas.bhole@iona.com>

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=20

> -----Original Message-----
> From: Ulhas Bhole [mailto:ulhas.bhole@iona.com]=20
> Sent: Friday, November 17, 2006 11:41 AM
> To: cxf-dev@incubator.apache.org
> Subject: RE: JMS WSDL question
>=20
> Hi Eric,
>=20
> Here is the sample attached of the old client that shows how=20
> it was used.=20
>=20
> I am not sure whether current code supports the same model to=20
> access JMS context info. On other thing to clarify on the=20
> WSDL, configuration, and JMS-context stuff is that JMS WSDL=20
> extensors can be configured via Configuration but some=20
> configuration specific stuff like session pool size cannot be=20
> set in WSDL and same holds true for context info. which=20
> cannot be set via WSDL or configuration.
>=20
> Regards,
>=20
> Ulhas Bhole
>=20
> On Fri, 2006-11-17 at 16:12 +0000, Ulhas Bhole wrote:
> > Hi Eric,
> >=20
> > It needs to be set programmatically and very few of the=20
> attributes are
> > settable. It is set through   RequestContext and can be=20
> retrived from
> > respose via ResponseContext.
> >=20
> > If you want the exact mechanism you will need to search for=20
> some old=20
> > installer of celtix (pre-apache) and look at the JMS samples.
> >=20
> > Regards,
> >=20
> > Ulhas Bhole
> >=20
> > 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=20
> attributes such=20
> > > as JMSPriority. Do I do it in the WSDL using the elements=20
> defined in=20
> > > the jms-context namespace? Is there a way to do this=20
> programmatically?
> > > Cheers,
> > > Eric
> > >=20
> > > > -----Original Message-----
> > > > From: Willem Jiang [mailto:ning.jiang@iona.com]
> > > > Sent: Thursday, November 16, 2006 8:40 PM
> > > > To: cxf-dev@incubator.apache.org
> > > > Subject: Re: JMS WSDL question
> > > >=20
> > > > Hi Eric,
> > > >=20
> > > > I do a quick look into the code, I think current CXF doesn't=20
> > > > support get the header properties from configuration, because=20
> > > > 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 =20
> JMS Context=20
> > > > Mechanism.
> > > > Is it  the same question with this header issue?
> > > > There are both "Context" related  jms-context element and maybe=20
> > > > some kind of Message context :)
> > > >=20
> > > > Cheers,
> > > > Willem.
> > > > =20
> > > >=20
> > > > Johnson, Eric wrote:
> > > >=20
> > > > >Willem,
> > > > >So I can use the jms-context elements in the WSDL to=20
> specify the=20
> > > > >JMS header properties? Can I also place them in the=20
> configuration file?
> > > > >Are there examples?
> > > > >Cheers,
> > > > >Eric
> > > > >=20
> > > > >
> > > > > =20
> > > > >
> > > > >>-----Original Message-----
> > > > >>From: Willem Jiang [mailto:ning.jiang@iona.com]
> > > > >>Sent: Thursday, November 16, 2006 8:07 PM
> > > > >>To: cxf-dev@incubator.apache.org
> > > > >>Subject: Re: JMS WSDL question
> > > > >>
> > > > >>Hi Eric,
> > > > >>
> > > > >>You can find the schema of the jms WSDL extensions from=20
> > > >=20
> >>trunk/common/schemas/src/main/resources/schemas/wsdl/jms-context
> > > > >>.xsd
> > > > >>and
> > > >=20
> >>trunk/common/schemas/src/main/resources/schemas/wsdl/jms-conf.xs
> > > > >>d
> > > > >>
> > > > >>
> > > > >>Willem.
> > > > >>
> > > > >>Johnson, Eric wrote:
> > > > >>
> > > > >>   =20
> > > > >>
> > > > >>>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?
> > > > >>>
> > > > >>>=20
> > > > >>>
> > > > >>>     =20
> > > > >>>
> > > > >>   =20
> > > > >>
> > > > >
> > > > > =20
> > > > >
> > > >=20
> > > >=20
>=20