Correct.  Generic JMS stuff is OK to have in the JAR, but any vendor-specific stuff 
like Sonic/IBM/etc is not, at least as far as I'm concerned.  Other opinions?

--Glen

> -----Original Message-----
> From: Jaime Meritt [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 06, 2003 3:24 PM
> To: [EMAIL PROTECTED]
> Subject: RE: JMS transport not in 1.1 binary distribution
> 
> 
> Glen,
> 
> Great, thanks a lot for the help.  To get the SonicMQVendorAdapter to
> build you will need the SonicMQ client jars available as 
> well.  What is
> the current policy on third party library dependencies?  Does 
> the binary
> distribution include all options or just the default packages?  If it
> includes all options, I can send you Sonic client libraries for build
> purposes.  If not, I am assuming the solution is to have users build
> from the source distribution.
> 
> Thanks,
> Jaime 
> 
> -----Original Message-----
> From: Glen Daniels [mailto:[EMAIL PROTECTED]] 
> Sent: Monday, January 06, 2003 2:14 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: JMS transport not in 1.1 binary distribution
> 
> 
> Actually, I did (JRun's), and have no idea why it wasn't in there.
> 
> I'll rebuild and repost, though, as beta2.  We should get 1.1 up to
> speed and out soon!
> 
> --Glen
> 
> > -----Original Message-----
> > From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, January 06, 2003 2:11 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: JMS transport not in 1.1 binary distribution
> > 
> > 
> > Jaime,
> > 
> > The release builds are built by the release manager (in 
> > 1.1beta1, that was Glen) and this person has to have all of 
> > the jar files around to get the right build thing to happen.
> > 
> > My guess is that Glen did NOT have a JMS jar on his system 
> > when building 1.1.
> > 
> > --
> > Tom Jordahl
> > Macromedia Server Development
> > 
> > 
> > 
> > -----Original Message-----
> > From: Jaime Meritt [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, January 02, 2003 1:24 PM
> > To: [EMAIL PROTECTED]
> > Subject: JMS transport not in 1.1 binary distribution
> > 
> > 
> > Hi,
> > 
> > I just got an email from a user alerting me to the fact that the JMS
> > transport classes are not included in the binary 
> distribution for the
> > Axis 1.1 beta.  It is however available in the source 
> > distribution.  Can
> > anyone shed some light on this?  I would imagine that the 
> JMS classes
> > were unavailable when the distribution was built.  Who can 
> modify the
> > build classpath?  
> > 
> > Thanks,
> > Jaime
> > ---
> > Jaime Meritt
> > Manager, Software Engineering
> > Sonic Software Corporation
> > 400 Technology Square
> > Progress Software Suite
> > Cambridge, MA 02139
> > Phone: 617-551-6613
> >  
> > 
> 

Reply via email to