Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
Message-ID: 
 <CB1FF0A474AEA84EA0206D5B05F6A4CB030A39CC@S1001EXM02.macromedia.com>
From: Glen Daniels <gdaniels@macromedia.com>
To: "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
Subject: RE: JMS transport not in 1.1 binary distribution
Date: Mon, 6 Jan 2003 14:13:41 -0500 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"


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:tomj@macromedia.com]
> Sent: Monday, January 06, 2003 2:11 PM
> To: 'axis-dev@xml.apache.org'
> 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:jmeritt@sonicsoftware.com]
> Sent: Thursday, January 02, 2003 1:24 PM
> To: axis-dev@xml.apache.org
> 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
>  
>