m Jordahl <[EMAIL PROTECTED]>
01/08/2003 07:35 AM
Please respond to axis-dev
To
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc
bcc
Subject
RE: JMS transport not in 1.1 binary distribution
I agree with Dims, I don't think we want to get to far down the DLL/J
- Original Message -
From: "Jaime Meritt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 06:13
Subject: RE: JMS transport not in 1.1 binary distribution
> Steve,
>
> +1 to the extensions directory. If this is created I wo
8:46 PM
To: [EMAIL PROTECTED]
Subject: Re: JMS transport not in 1.1 binary distribution
- Original Message -
From: "James M Snell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 06, 2003 21:11
Subject: RE: JMS transport not in 1.1 binary distribution
e the build process. For the next point release
we can pursue the generic extensions mechanisms you propose. Comments?
Thanks,
Jaime
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 8:46 PM
To: [EMAIL PROTECTED]
Subject: Re: JMS transpor
- Original Message -
From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 05:11
Subject: RE: JMS transport not in 1.1 binary distribution
> My idea of Jar-Hell :( Just like DLL's/SharedObject's Hell
- Original Message -
From: "James M Snell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 06, 2003 21:11
Subject: RE: JMS transport not in 1.1 binary distribution
> Btw, I personally think that individual Axis transports should be put into
&
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 06, 2003 17:54
Subject: RE: JMS transport not in 1.1 binary distribution
>
>
>
>
> The ideal solution would be for me as a user to simpl
- Original Message -
From: "Glen Daniels" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 06, 2003 11:13
Subject: RE: JMS transport not in 1.1 binary distribution
>
> Actually, I did (JRun's), and have no idea why it wasn't in th
your
> God will be with you whereever you go.- Joshua 1:9
>
>
>
> [EMAIL PROTECTED]
> 01/06/2003 05:54 PM
> Please respond to axis-dev
>
>
> To
> [EMAIL PROTECTED]
> cc
> "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> bcc
>
you go.- Joshua 1:9
>
>
>
> [EMAIL PROTECTED]
> 01/06/2003 05:54 PM
> Please respond to axis-dev
>
>
> To
> [EMAIL PROTECTED]
> cc
> "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> bcc
>
> Subject
> RE: JMS transport not
e terrified, do not be discouraged, for the Lord your
God will be with you whereever you go.- Joshua 1:9
[EMAIL PROTECTED]
01/06/2003 05:54 PM
Please respond to axis-dev
To
[EMAIL PROTECTED]
cc
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
bcc
Subject
RE:
aniels To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> cc: (bcc: Kevin
Bedell/Systems/USHO/SunLife)
01/06/2003 03:39 P
handle the generic Ant work to set it up (I
would do that too, but I'm not too great with Ant).
Thanks,
Jaime
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 06, 2003 3:39 PM
To: '[EMAIL PROTECTED]'
Subject: RE: JMS transport not in 1.1 b
Well, I agree with you. I don't think you should need to build from source to use
third-party stuff. But nor do I think we should have any in axis.jar.
I haven't really looked at the JMS transport stuff yet, but I'm assuming that there's
just a setting (engine property /
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject: RE: JMS transport not in 1.1 binary distribution
So out of the box Axis can't be used with any specific JMS implementations?
This seems like it would impede adoption.
If I have to build from source, does that mean using a nigh
To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> cc: (bcc: Kevin
Bedell/Systems/USHO/SunLife)
01/06/2003 03:25 PM
3 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 curren
: '[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-
03 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 ge
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
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
All,
Attached is a minor patch to the JMS transport. It includes a first cut
at a vendor-specific exception handling mechanism. This extension
allows the JMS connector to fail-fast when it encounters vendor specific
exceptions that cannot be recovered from. The old behavior was to retry
for a
ge-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, September 25, 2002 7:27 PM
> > To: [EMAIL PROTECTED]
> > Subject: Updated documentation files for JMS transport.
> >
> > Hi all,
> > I have updated user-guide.html and arch
rom: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, September 25, 2002 7:27 PM
> > To: [EMAIL PROTECTED]
> > Subject: Updated documentation files for JMS transport.
> >
> > Hi all,
> > I have updated user-guide.html and architecture-guide.html to
m.
> --
> Tom Jordahl
> Macromedia
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 25, 2002 7:27 PM
> To: [EMAIL PROTECTED]
> Subject: Updated documentation files for JMS transport.
>
> Hi all,
> I
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 7:27 PM
To: [EMAIL PROTECTED]
Subject: Updated documentation files for JMS transport.
Hi all,
I have updated user-guide.html and architecture-guide.html to make
references to JMS where appropriate. I also updated the
Hi all,
I have updated user-guide.html and architecture-guide.html to make
references to JMS where appropriate. I also updated the diagram in
subsystems.jpg (in attached zip file) to reflect JMS as one of the
tranpsport options alongside of HTTP and SMTP. Attached are the files
and a diff, if a
nto the main
> > tree.
> > Dave
> >
> >
> > Jaime Meritt wrote:
> > >
> > > Sure, the new file is attached.
> > > Thanks for the help,
> > > Jaime
> > >
> > > -Original Message-
> > > From: Davanum Srinivas [mai
> Sure, the new file is attached.
> > > Thanks for the help,
> > > Jaime
> > >
> > > -Original Message-
> > > From: Davanum Srinivas [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, September 20, 2002 11:01 AM
> > > To: [EMAIL P
rinivas [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, September 20, 2002 11:01 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: JMS Transport Patch
> >
> > Jaime,
> >
> > Can you please do the following
> > - Use "cvs diff -u" from xml-ax
d.
> Thanks for the help,
> Jaime
>
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 20, 2002 11:01 AM
> To: [EMAIL PROTECTED]
> Subject: Re: JMS Transport Patch
>
> Jaime,
>
> Can you please do the fol
Sure, the new file is attached.
Thanks for the help,
Jaime
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 20, 2002 11:01 AM
To: [EMAIL PROTECTED]
Subject: Re: JMS Transport Patch
Jaime,
Can you please do the following
- Use "cvs di
e zip file preserves text from
getting
clobbered.
--- Jaime Meritt <[EMAIL PROTECTED]> wrote:
> All,
>
> Attached is a patch that makes the modifications to the JMS transport
> that we discussed in the Tuesday IRC chat. Mainly, it removes the
> SonicMQ usage from the sample c
The JMS transport patch I submitted yesterday successfully runs with
all-tests now that the WSDL test modifications have been made. Thanks
for the extremely fast turnaround time on this.
Thanks,
Jaime
All,
Attached is a patch that makes the modifications to the JMS transport
that we discussed in the Tuesday IRC chat. Mainly, it removes the
SonicMQ usage from the sample code and replaces it with JNDI.
Furthermore I have introduced a pluggable JMS vendor component that is
used for vendor
Russ,
You could start with the basic information in [1].
I wonder if NYI stands for "not yet implemented"?
Glyn
[1] http://www.mail-archive.com/axis-dev@xml.apache.org/msg01360.html
Although I have just discovered axis, I would like to
help build the JMS transport/listener/sender. I was
wondering what the steps are to getting involved at
this level. Any info would be appreciated.
Thanks,
Russ
BTW: I don't know what NYI
37 matches
Mail list logo
