You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Luis Rivera <lu...@hotmail.com> on 2006/07/07 04:47:16 UTC
[Axis 1.4] Server side question !!!
Hi axis users,
I finally got the green light to port the server side or our web services
from LEIF/Roguewave to axis. The main reason is economics, we want to
explore cheaper options.
I was exploring the alternatives for serverlet containers in the server
side, which will be Windows/Solaris. I think the best for axis is Tomcat,
but I am confused with regard to the version I am supposed to use or if this
is the way to go.
I also looked into Sun Application Server (J2EE based I believe) but why
would I do that? It seems that I would not need axis if I used Sun
Application Server.
So, if I had to justify axis/Tomcat vs J2EE, what would be the best
arguments in favor of axis?
Thanks in advance,
--Luis R.
_________________________________________________________________
Dont just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] Server side question !!!
Posted by Martin Gainty <mg...@hotmail.com>.
Luis-
*If* you write your own connector you can configure it in as a Connector in $TOMCAT_HOME/conf/server.xml
here is an example of the default Port 8080 connector..
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector
port="8080" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
Anyone else?
M-
*********************************************************************
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message -----
From: "Luis Rivera" <lu...@hotmail.com>
To: <ax...@ws.apache.org>
Sent: Friday, July 14, 2006 5:35 PM
Subject: Re: [Axis 1.4] Server side question !!!
>
>
> Hi again Axis-Users/Devs,
>
> I have another couple of questions:
>
> Fisrt of all, after installing Tomcat and figuring out how to deploy my
> application, I have sucessfully made my first client call to the empty
> implementation. However, the original server side implementation (c++
> RogueWave) uses 4 different ports, one for each bindings (4 of them). Now
> with Tomcat I have only one and I am using a different path to each binding,
> so
>
> 1) Can I configure Tomcat to use a different port for each service using a
> different Connector for each one?
>
> Second, my application will be accessed by the axis implementation via JNI.
> I have read on the web that they should not be placed in the
> webapps/axis/classes directory to avoid classloading problems of the static
> llibrary. But if placing them in the shared/lib directory is not where I can
> to place them,
>
> 2) How can I make tomcat look into the directory where I want to place them?
> (both in Windows/Solaris)? .. .should I just include them into the path?
>
> Thanks in advance,
> --Luis R.
>
>
>>From: "Anne Thomas Manes" <at...@gmail.com>
>>Reply-To: axis-user@ws.apache.org
>>To: axis-user@ws.apache.org
>>Subject: Re: [Axis 1.4] Server side question !!!
>>Date: Fri, 7 Jul 2006 18:12:54 -0400
>>
>>Go with Tomcat 5.5.
>>
>>On 7/7/06, Luis Rivera <lu...@hotmail.com> wrote:
>>>
>>> Hi Anne,
>>>
>>>Fair enough and thanks agan :) ... I also think J2EE is overkill. Now,
>>>what
>>>versino of Tomcat should I use? 5.5 is the one I downloaded, but it seems
>>>from the axis documentation they recomend 4.1. In any way it seems that
>>>configuring and deploying in Solaris are the trickiest parts of all this.
>>>
>>>The systinet idea was already explored here, but I guess they want to go
>>>on
>>>the cheap. I guess it is up to me to prove that this can be done in a
>>>fairly
>>>reasonable amount of time and with the smallest impact to the current
>>>implementation.
>>>
>>> Thanks in advance,
>>> --Luis R.
>>>
>>>
>>> >From: "Anne Thomas Manes" <at...@gmail.com>
>>> >Reply-To: axis-user@ws.apache.org
>>> >To: axis-user@ws.apache.org
>>> >Subject: Re: [Axis 1.4] Server side question !!!
>>> >Date: Fri, 7 Jul 2006 16:40:29 -0400
>>> >
>>> >If you don't plan to use all the crap -- I mean features -- that comes
>>> >bundled with J2EE, then I see no reason whatsoever to use J2EE. If
>>> >your goal is simply to provide a very thin JNI veneer over your
>>> >existing C++ apps, then Axis/Tomcat is a much better, more
>>> >stream-lined solution.
>>> >
>>> >The only other suggestion that I recommend you explore is Systinet
>>> >Server for C++ (see http://www.systinet.com/products/ssc/overview).
>>> >It's not open source, but it is less expensive than LEIF.
>>> >
>>> >Anne
>>> >
>>> >On 7/7/06, Luis Rivera <lu...@hotmail.com> wrote:
>>> >>
>>> >>First of all, thanks for the reply Anne, I appreciate it :)
>>> >>
>>> >>We already looked into C/C++ axis, but it is clearly not mature and
>>>full
>>> >>of
>>> >>bugs. That let us with two choices:
>>> >>
>>> >>1) As you said, rewrite the whole server side in Java ... let's just
>>>say
>>> >>this was not even a real option.
>>> >>
>>> >>2) Write a thin server side in Java with JNI as the bridge to the
>>>already
>>> >>existing code in C++. The current architecture of the application
>>>allows a
>>> >>simple substiution of the SOAP layer with a Java version, using the
>>> >>proxies
>>> >>behind to bridge the rest of the application.
>>> >>
>>> >>So, the server side in this case should be fairly simple, but I wanted
>>>to
>>> >>know what made more sense for deployment knowing that the server side
>>>can
>>> >>either be Solaris/Windows and in the near future Linux. I looked first
>>> >>into
>>> >>axis because I had the clients alredy using axis and it seemed to me
>>>that
>>> >>having axis in both sides could simplyfy the task, but I may be wrong.
>>> >>
>>> >>So, let me ask again, knowing that I will use Java/JNI, is axis/Tomcat
>>> >>better or at least comparable to J2EE?
>>> >>
>>> >> Again, thanks in advance,
>>> >> --Luis R.
>>> >>
>>> >> >From: "Anne Thomas Manes" <at...@gmail.com>
>>> >> >Reply-To: axis-user@ws.apache.org
>>> >> >To: axis-user@ws.apache.org
>>> >> >Subject: Re: [Axis 1.4] Server side question !!!
>>> >> >Date: Fri, 7 Jul 2006 08:53:44 -0400
>>> >> >
>>> >> >Axis supports C/C++. Given that you've been using LEIF, I assume that
>>> >> >your services are written in C/C++. Do you intend to rewrite all your
>>> >> >apps?
>>> >> >
>>> >> >Axis for Java can run in any servlet engine -- including any J2EE
>>> >> >server. It's true that Sun's J2EE server includes a SOAP engine, but
>>> >> >it doesn't support C/C++. Assuming that you really don't want to
>>> >> >reimplement all your apps, Axis provides you with a common SOAP
>>> >> >architecture that supports both Java and C++.
>>> >> >
>>> >> >Anne
>>> >> >
>>> >> >On 7/6/06, Luis Rivera <lu...@hotmail.com> wrote:
>>> >> >>
>>> >> >> Hi axis users,
>>> >> >>
>>> >> >>I finally got the green light to port the server side or our web
>>> >>services
>>> >> >>from LEIF/Roguewave to axis. The main reason is economics, we want
>>>to
>>> >> >>explore cheaper options.
>>> >> >>
>>> >> >>I was exploring the alternatives for serverlet containers in the
>>>server
>>> >> >>side, which will be Windows/Solaris. I think the best for axis is
>>> >>Tomcat,
>>> >> >>but I am confused with regard to the version I am supposed to use or
>>>if
>>> >> >>this
>>> >> >>is the way to go.
>>> >> >>
>>> >> >>I also looked into Sun Application Server (J2EE based I believe)
>>>but
>>> >>why
>>> >> >>would I do that? It seems that I would not need axis if I used Sun
>>> >> >>Application Server.
>>> >> >>
>>> >> >>So, if I had to justify axis/Tomcat vs J2EE, what would be the best
>>> >> >>arguments in favor of axis?
>>> >> >>
>>> >> >> Thanks in advance,
>>> >> >> --Luis R.
>>> >> >>
>>> >> >>_________________________________________________________________
>>> >> >>Don't just search. Find. Check out the new MSN Search!
>>> >> >>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>>> >> >>
>>> >> >>
>>> >>
>>> >>---------------------------------------------------------------------
>>> >> >>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> >> >>For additional commands, e-mail: axis-user-help@ws.apache.org
>>> >> >>
>>> >> >>
>>> >> >
>>> >> >---------------------------------------------------------------------
>>> >> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> >> >For additional commands, e-mail: axis-user-help@ws.apache.org
>>> >> >
>>> >>
>>> >>_________________________________________________________________
>>> >>Is your PC infected? Get a FREE online computer virus scan from
>>>McAfee(r)
>>> >>Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>>> >>
>>> >>
>>> >>---------------------------------------------------------------------
>>> >>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> >>For additional commands, e-mail: axis-user-help@ws.apache.org
>>> >>
>>> >>
>>> >
>>> >---------------------------------------------------------------------
>>> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> >For additional commands, e-mail: axis-user-help@ws.apache.org
>>> >
>>>
>>>_________________________________________________________________
>>>Is your PC infected? Get a FREE online computer virus scan from McAfee(r)
>>>Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
> _________________________________________________________________
> On the road to retirement? Check out MSN Life Events for advice on how to
> get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: [Axis 1.4] Server side question !!!
Posted by Luis Rivera <lu...@hotmail.com>.
Hi again Axis-Users/Devs,
I have another couple of questions:
Fisrt of all, after installing Tomcat and figuring out how to deploy my
application, I have sucessfully made my first client call to the empty
implementation. However, the original server side implementation (c++
RogueWave) uses 4 different ports, one for each bindings (4 of them). Now
with Tomcat I have only one and I am using a different path to each binding,
so
1) Can I configure Tomcat to use a different port for each service using a
different Connector for each one?
Second, my application will be accessed by the axis implementation via JNI.
I have read on the web that they should not be placed in the
webapps/axis/classes directory to avoid classloading problems of the static
llibrary. But if placing them in the shared/lib directory is not where I can
to place them,
2) How can I make tomcat look into the directory where I want to place them?
(both in Windows/Solaris)? .. .should I just include them into the path?
Thanks in advance,
--Luis R.
>From: "Anne Thomas Manes" <at...@gmail.com>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: Re: [Axis 1.4] Server side question !!!
>Date: Fri, 7 Jul 2006 18:12:54 -0400
>
>Go with Tomcat 5.5.
>
>On 7/7/06, Luis Rivera <lu...@hotmail.com> wrote:
>>
>> Hi Anne,
>>
>>Fair enough and thanks agan :) ... I also think J2EE is overkill. Now,
>>what
>>versino of Tomcat should I use? 5.5 is the one I downloaded, but it seems
>>from the axis documentation they recomend 4.1. In any way it seems that
>>configuring and deploying in Solaris are the trickiest parts of all this.
>>
>>The systinet idea was already explored here, but I guess they want to go
>>on
>>the cheap. I guess it is up to me to prove that this can be done in a
>>fairly
>>reasonable amount of time and with the smallest impact to the current
>>implementation.
>>
>> Thanks in advance,
>> --Luis R.
>>
>>
>> >From: "Anne Thomas Manes" <at...@gmail.com>
>> >Reply-To: axis-user@ws.apache.org
>> >To: axis-user@ws.apache.org
>> >Subject: Re: [Axis 1.4] Server side question !!!
>> >Date: Fri, 7 Jul 2006 16:40:29 -0400
>> >
>> >If you don't plan to use all the crap -- I mean features -- that comes
>> >bundled with J2EE, then I see no reason whatsoever to use J2EE. If
>> >your goal is simply to provide a very thin JNI veneer over your
>> >existing C++ apps, then Axis/Tomcat is a much better, more
>> >stream-lined solution.
>> >
>> >The only other suggestion that I recommend you explore is Systinet
>> >Server for C++ (see http://www.systinet.com/products/ssc/overview).
>> >It's not open source, but it is less expensive than LEIF.
>> >
>> >Anne
>> >
>> >On 7/7/06, Luis Rivera <lu...@hotmail.com> wrote:
>> >>
>> >>First of all, thanks for the reply Anne, I appreciate it :)
>> >>
>> >>We already looked into C/C++ axis, but it is clearly not mature and
>>full
>> >>of
>> >>bugs. That let us with two choices:
>> >>
>> >>1) As you said, rewrite the whole server side in Java ... let's just
>>say
>> >>this was not even a real option.
>> >>
>> >>2) Write a thin server side in Java with JNI as the bridge to the
>>already
>> >>existing code in C++. The current architecture of the application
>>allows a
>> >>simple substiution of the SOAP layer with a Java version, using the
>> >>proxies
>> >>behind to bridge the rest of the application.
>> >>
>> >>So, the server side in this case should be fairly simple, but I wanted
>>to
>> >>know what made more sense for deployment knowing that the server side
>>can
>> >>either be Solaris/Windows and in the near future Linux. I looked first
>> >>into
>> >>axis because I had the clients alredy using axis and it seemed to me
>>that
>> >>having axis in both sides could simplyfy the task, but I may be wrong.
>> >>
>> >>So, let me ask again, knowing that I will use Java/JNI, is axis/Tomcat
>> >>better or at least comparable to J2EE?
>> >>
>> >> Again, thanks in advance,
>> >> --Luis R.
>> >>
>> >> >From: "Anne Thomas Manes" <at...@gmail.com>
>> >> >Reply-To: axis-user@ws.apache.org
>> >> >To: axis-user@ws.apache.org
>> >> >Subject: Re: [Axis 1.4] Server side question !!!
>> >> >Date: Fri, 7 Jul 2006 08:53:44 -0400
>> >> >
>> >> >Axis supports C/C++. Given that you've been using LEIF, I assume that
>> >> >your services are written in C/C++. Do you intend to rewrite all your
>> >> >apps?
>> >> >
>> >> >Axis for Java can run in any servlet engine -- including any J2EE
>> >> >server. It's true that Sun's J2EE server includes a SOAP engine, but
>> >> >it doesn't support C/C++. Assuming that you really don't want to
>> >> >reimplement all your apps, Axis provides you with a common SOAP
>> >> >architecture that supports both Java and C++.
>> >> >
>> >> >Anne
>> >> >
>> >> >On 7/6/06, Luis Rivera <lu...@hotmail.com> wrote:
>> >> >>
>> >> >> Hi axis users,
>> >> >>
>> >> >>I finally got the green light to port the server side or our web
>> >>services
>> >> >>from LEIF/Roguewave to axis. The main reason is economics, we want
>>to
>> >> >>explore cheaper options.
>> >> >>
>> >> >>I was exploring the alternatives for serverlet containers in the
>>server
>> >> >>side, which will be Windows/Solaris. I think the best for axis is
>> >>Tomcat,
>> >> >>but I am confused with regard to the version I am supposed to use or
>>if
>> >> >>this
>> >> >>is the way to go.
>> >> >>
>> >> >>I also looked into Sun Application Server (J2EE based I believe)
>>but
>> >>why
>> >> >>would I do that? It seems that I would not need axis if I used Sun
>> >> >>Application Server.
>> >> >>
>> >> >>So, if I had to justify axis/Tomcat vs J2EE, what would be the best
>> >> >>arguments in favor of axis?
>> >> >>
>> >> >> Thanks in advance,
>> >> >> --Luis R.
>> >> >>
>> >> >>_________________________________________________________________
>> >> >>Don't just search. Find. Check out the new MSN Search!
>> >> >>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>> >> >>
>> >> >>
>> >>
>> >>---------------------------------------------------------------------
>> >> >>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> >>For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >---------------------------------------------------------------------
>> >> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> >For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >
>> >>
>> >>_________________________________________________________________
>> >>Is your PC infected? Get a FREE online computer virus scan from
>>McAfee(r)
>> >>Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>> >>
>> >>
>> >>---------------------------------------------------------------------
>> >>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >>For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>>
>>_________________________________________________________________
>>Is your PC infected? Get a FREE online computer virus scan from McAfee(r)
>>Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] Server side question !!!
Posted by Anne Thomas Manes <at...@gmail.com>.
Go with Tomcat 5.5.
On 7/7/06, Luis Rivera <lu...@hotmail.com> wrote:
>
> Hi Anne,
>
> Fair enough and thanks agan :) ... I also think J2EE is overkill. Now, what
> versino of Tomcat should I use? 5.5 is the one I downloaded, but it seems
> from the axis documentation they recomend 4.1. In any way it seems that
> configuring and deploying in Solaris are the trickiest parts of all this.
>
> The systinet idea was already explored here, but I guess they want to go on
> the cheap. I guess it is up to me to prove that this can be done in a fairly
> reasonable amount of time and with the smallest impact to the current
> implementation.
>
> Thanks in advance,
> --Luis R.
>
>
> >From: "Anne Thomas Manes" <at...@gmail.com>
> >Reply-To: axis-user@ws.apache.org
> >To: axis-user@ws.apache.org
> >Subject: Re: [Axis 1.4] Server side question !!!
> >Date: Fri, 7 Jul 2006 16:40:29 -0400
> >
> >If you don't plan to use all the crap -- I mean features -- that comes
> >bundled with J2EE, then I see no reason whatsoever to use J2EE. If
> >your goal is simply to provide a very thin JNI veneer over your
> >existing C++ apps, then Axis/Tomcat is a much better, more
> >stream-lined solution.
> >
> >The only other suggestion that I recommend you explore is Systinet
> >Server for C++ (see http://www.systinet.com/products/ssc/overview).
> >It's not open source, but it is less expensive than LEIF.
> >
> >Anne
> >
> >On 7/7/06, Luis Rivera <lu...@hotmail.com> wrote:
> >>
> >>First of all, thanks for the reply Anne, I appreciate it :)
> >>
> >>We already looked into C/C++ axis, but it is clearly not mature and full
> >>of
> >>bugs. That let us with two choices:
> >>
> >>1) As you said, rewrite the whole server side in Java ... let's just say
> >>this was not even a real option.
> >>
> >>2) Write a thin server side in Java with JNI as the bridge to the already
> >>existing code in C++. The current architecture of the application allows a
> >>simple substiution of the SOAP layer with a Java version, using the
> >>proxies
> >>behind to bridge the rest of the application.
> >>
> >>So, the server side in this case should be fairly simple, but I wanted to
> >>know what made more sense for deployment knowing that the server side can
> >>either be Solaris/Windows and in the near future Linux. I looked first
> >>into
> >>axis because I had the clients alredy using axis and it seemed to me that
> >>having axis in both sides could simplyfy the task, but I may be wrong.
> >>
> >>So, let me ask again, knowing that I will use Java/JNI, is axis/Tomcat
> >>better or at least comparable to J2EE?
> >>
> >> Again, thanks in advance,
> >> --Luis R.
> >>
> >> >From: "Anne Thomas Manes" <at...@gmail.com>
> >> >Reply-To: axis-user@ws.apache.org
> >> >To: axis-user@ws.apache.org
> >> >Subject: Re: [Axis 1.4] Server side question !!!
> >> >Date: Fri, 7 Jul 2006 08:53:44 -0400
> >> >
> >> >Axis supports C/C++. Given that you've been using LEIF, I assume that
> >> >your services are written in C/C++. Do you intend to rewrite all your
> >> >apps?
> >> >
> >> >Axis for Java can run in any servlet engine -- including any J2EE
> >> >server. It's true that Sun's J2EE server includes a SOAP engine, but
> >> >it doesn't support C/C++. Assuming that you really don't want to
> >> >reimplement all your apps, Axis provides you with a common SOAP
> >> >architecture that supports both Java and C++.
> >> >
> >> >Anne
> >> >
> >> >On 7/6/06, Luis Rivera <lu...@hotmail.com> wrote:
> >> >>
> >> >> Hi axis users,
> >> >>
> >> >>I finally got the green light to port the server side or our web
> >>services
> >> >>from LEIF/Roguewave to axis. The main reason is economics, we want to
> >> >>explore cheaper options.
> >> >>
> >> >>I was exploring the alternatives for serverlet containers in the server
> >> >>side, which will be Windows/Solaris. I think the best for axis is
> >>Tomcat,
> >> >>but I am confused with regard to the version I am supposed to use or if
> >> >>this
> >> >>is the way to go.
> >> >>
> >> >>I also looked into Sun Application Server (J2EE based I believe) but
> >>why
> >> >>would I do that? It seems that I would not need axis if I used Sun
> >> >>Application Server.
> >> >>
> >> >>So, if I had to justify axis/Tomcat vs J2EE, what would be the best
> >> >>arguments in favor of axis?
> >> >>
> >> >> Thanks in advance,
> >> >> --Luis R.
> >> >>
> >> >>_________________________________________________________________
> >> >>Don't just search. Find. Check out the new MSN Search!
> >> >>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> >> >>
> >> >>
> >> >>---------------------------------------------------------------------
> >> >>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >>For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >>
> >> >>
> >> >
> >> >---------------------------------------------------------------------
> >> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >
> >>
> >>_________________________________________________________________
> >>Is your PC infected? Get a FREE online computer virus scan from McAfee(r)
> >>Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >>For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
> _________________________________________________________________
> Is your PC infected? Get a FREE online computer virus scan from McAfee(r)
> Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] Server side question !!!
Posted by Luis Rivera <lu...@hotmail.com>.
Hi Anne,
Fair enough and thanks agan :) ... I also think J2EE is overkill. Now, what
versino of Tomcat should I use? 5.5 is the one I downloaded, but it seems
from the axis documentation they recomend 4.1. In any way it seems that
configuring and deploying in Solaris are the trickiest parts of all this.
The systinet idea was already explored here, but I guess they want to go on
the cheap. I guess it is up to me to prove that this can be done in a fairly
reasonable amount of time and with the smallest impact to the current
implementation.
Thanks in advance,
--Luis R.
>From: "Anne Thomas Manes" <at...@gmail.com>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: Re: [Axis 1.4] Server side question !!!
>Date: Fri, 7 Jul 2006 16:40:29 -0400
>
>If you don't plan to use all the crap -- I mean features -- that comes
>bundled with J2EE, then I see no reason whatsoever to use J2EE. If
>your goal is simply to provide a very thin JNI veneer over your
>existing C++ apps, then Axis/Tomcat is a much better, more
>stream-lined solution.
>
>The only other suggestion that I recommend you explore is Systinet
>Server for C++ (see http://www.systinet.com/products/ssc/overview).
>It's not open source, but it is less expensive than LEIF.
>
>Anne
>
>On 7/7/06, Luis Rivera <lu...@hotmail.com> wrote:
>>
>>First of all, thanks for the reply Anne, I appreciate it :)
>>
>>We already looked into C/C++ axis, but it is clearly not mature and full
>>of
>>bugs. That let us with two choices:
>>
>>1) As you said, rewrite the whole server side in Java ... let's just say
>>this was not even a real option.
>>
>>2) Write a thin server side in Java with JNI as the bridge to the already
>>existing code in C++. The current architecture of the application allows a
>>simple substiution of the SOAP layer with a Java version, using the
>>proxies
>>behind to bridge the rest of the application.
>>
>>So, the server side in this case should be fairly simple, but I wanted to
>>know what made more sense for deployment knowing that the server side can
>>either be Solaris/Windows and in the near future Linux. I looked first
>>into
>>axis because I had the clients alredy using axis and it seemed to me that
>>having axis in both sides could simplyfy the task, but I may be wrong.
>>
>>So, let me ask again, knowing that I will use Java/JNI, is axis/Tomcat
>>better or at least comparable to J2EE?
>>
>> Again, thanks in advance,
>> --Luis R.
>>
>> >From: "Anne Thomas Manes" <at...@gmail.com>
>> >Reply-To: axis-user@ws.apache.org
>> >To: axis-user@ws.apache.org
>> >Subject: Re: [Axis 1.4] Server side question !!!
>> >Date: Fri, 7 Jul 2006 08:53:44 -0400
>> >
>> >Axis supports C/C++. Given that you've been using LEIF, I assume that
>> >your services are written in C/C++. Do you intend to rewrite all your
>> >apps?
>> >
>> >Axis for Java can run in any servlet engine -- including any J2EE
>> >server. It's true that Sun's J2EE server includes a SOAP engine, but
>> >it doesn't support C/C++. Assuming that you really don't want to
>> >reimplement all your apps, Axis provides you with a common SOAP
>> >architecture that supports both Java and C++.
>> >
>> >Anne
>> >
>> >On 7/6/06, Luis Rivera <lu...@hotmail.com> wrote:
>> >>
>> >> Hi axis users,
>> >>
>> >>I finally got the green light to port the server side or our web
>>services
>> >>from LEIF/Roguewave to axis. The main reason is economics, we want to
>> >>explore cheaper options.
>> >>
>> >>I was exploring the alternatives for serverlet containers in the server
>> >>side, which will be Windows/Solaris. I think the best for axis is
>>Tomcat,
>> >>but I am confused with regard to the version I am supposed to use or if
>> >>this
>> >>is the way to go.
>> >>
>> >>I also looked into Sun Application Server (J2EE based I believe) but
>>why
>> >>would I do that? It seems that I would not need axis if I used Sun
>> >>Application Server.
>> >>
>> >>So, if I had to justify axis/Tomcat vs J2EE, what would be the best
>> >>arguments in favor of axis?
>> >>
>> >> Thanks in advance,
>> >> --Luis R.
>> >>
>> >>_________________________________________________________________
>> >>Don't just search. Find. Check out the new MSN Search!
>> >>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>> >>
>> >>
>> >>---------------------------------------------------------------------
>> >>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >>For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>>
>>_________________________________________________________________
>>Is your PC infected? Get a FREE online computer virus scan from McAfee(r)
>>Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfeeŽ
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] Server side question !!!
Posted by Anne Thomas Manes <at...@gmail.com>.
If you don't plan to use all the crap -- I mean features -- that comes
bundled with J2EE, then I see no reason whatsoever to use J2EE. If
your goal is simply to provide a very thin JNI veneer over your
existing C++ apps, then Axis/Tomcat is a much better, more
stream-lined solution.
The only other suggestion that I recommend you explore is Systinet
Server for C++ (see http://www.systinet.com/products/ssc/overview).
It's not open source, but it is less expensive than LEIF.
Anne
On 7/7/06, Luis Rivera <lu...@hotmail.com> wrote:
>
> First of all, thanks for the reply Anne, I appreciate it :)
>
> We already looked into C/C++ axis, but it is clearly not mature and full of
> bugs. That let us with two choices:
>
> 1) As you said, rewrite the whole server side in Java ... let's just say
> this was not even a real option.
>
> 2) Write a thin server side in Java with JNI as the bridge to the already
> existing code in C++. The current architecture of the application allows a
> simple substiution of the SOAP layer with a Java version, using the proxies
> behind to bridge the rest of the application.
>
> So, the server side in this case should be fairly simple, but I wanted to
> know what made more sense for deployment knowing that the server side can
> either be Solaris/Windows and in the near future Linux. I looked first into
> axis because I had the clients alredy using axis and it seemed to me that
> having axis in both sides could simplyfy the task, but I may be wrong.
>
> So, let me ask again, knowing that I will use Java/JNI, is axis/Tomcat
> better or at least comparable to J2EE?
>
> Again, thanks in advance,
> --Luis R.
>
> >From: "Anne Thomas Manes" <at...@gmail.com>
> >Reply-To: axis-user@ws.apache.org
> >To: axis-user@ws.apache.org
> >Subject: Re: [Axis 1.4] Server side question !!!
> >Date: Fri, 7 Jul 2006 08:53:44 -0400
> >
> >Axis supports C/C++. Given that you've been using LEIF, I assume that
> >your services are written in C/C++. Do you intend to rewrite all your
> >apps?
> >
> >Axis for Java can run in any servlet engine -- including any J2EE
> >server. It's true that Sun's J2EE server includes a SOAP engine, but
> >it doesn't support C/C++. Assuming that you really don't want to
> >reimplement all your apps, Axis provides you with a common SOAP
> >architecture that supports both Java and C++.
> >
> >Anne
> >
> >On 7/6/06, Luis Rivera <lu...@hotmail.com> wrote:
> >>
> >> Hi axis users,
> >>
> >>I finally got the green light to port the server side or our web services
> >>from LEIF/Roguewave to axis. The main reason is economics, we want to
> >>explore cheaper options.
> >>
> >>I was exploring the alternatives for serverlet containers in the server
> >>side, which will be Windows/Solaris. I think the best for axis is Tomcat,
> >>but I am confused with regard to the version I am supposed to use or if
> >>this
> >>is the way to go.
> >>
> >>I also looked into Sun Application Server (J2EE based I believe) but why
> >>would I do that? It seems that I would not need axis if I used Sun
> >>Application Server.
> >>
> >>So, if I had to justify axis/Tomcat vs J2EE, what would be the best
> >>arguments in favor of axis?
> >>
> >> Thanks in advance,
> >> --Luis R.
> >>
> >>_________________________________________________________________
> >>Don't just search. Find. Check out the new MSN Search!
> >>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >>For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
> _________________________________________________________________
> Is your PC infected? Get a FREE online computer virus scan from McAfee(r)
> Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] Server side question !!!
Posted by Luis Rivera <lu...@hotmail.com>.
First of all, thanks for the reply Anne, I appreciate it :)
We already looked into C/C++ axis, but it is clearly not mature and full of
bugs. That let us with two choices:
1) As you said, rewrite the whole server side in Java ... let's just say
this was not even a real option.
2) Write a thin server side in Java with JNI as the bridge to the already
existing code in C++. The current architecture of the application allows a
simple substiution of the SOAP layer with a Java version, using the proxies
behind to bridge the rest of the application.
So, the server side in this case should be fairly simple, but I wanted to
know what made more sense for deployment knowing that the server side can
either be Solaris/Windows and in the near future Linux. I looked first into
axis because I had the clients alredy using axis and it seemed to me that
having axis in both sides could simplyfy the task, but I may be wrong.
So, let me ask again, knowing that I will use Java/JNI, is axis/Tomcat
better or at least comparable to J2EE?
Again, thanks in advance,
--Luis R.
>From: "Anne Thomas Manes" <at...@gmail.com>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: Re: [Axis 1.4] Server side question !!!
>Date: Fri, 7 Jul 2006 08:53:44 -0400
>
>Axis supports C/C++. Given that you've been using LEIF, I assume that
>your services are written in C/C++. Do you intend to rewrite all your
>apps?
>
>Axis for Java can run in any servlet engine -- including any J2EE
>server. It's true that Sun's J2EE server includes a SOAP engine, but
>it doesn't support C/C++. Assuming that you really don't want to
>reimplement all your apps, Axis provides you with a common SOAP
>architecture that supports both Java and C++.
>
>Anne
>
>On 7/6/06, Luis Rivera <lu...@hotmail.com> wrote:
>>
>> Hi axis users,
>>
>>I finally got the green light to port the server side or our web services
>>from LEIF/Roguewave to axis. The main reason is economics, we want to
>>explore cheaper options.
>>
>>I was exploring the alternatives for serverlet containers in the server
>>side, which will be Windows/Solaris. I think the best for axis is Tomcat,
>>but I am confused with regard to the version I am supposed to use or if
>>this
>>is the way to go.
>>
>>I also looked into Sun Application Server (J2EE based I believe) but why
>>would I do that? It seems that I would not need axis if I used Sun
>>Application Server.
>>
>>So, if I had to justify axis/Tomcat vs J2EE, what would be the best
>>arguments in favor of axis?
>>
>> Thanks in advance,
>> --Luis R.
>>
>>_________________________________________________________________
>>Don't just search. Find. Check out the new MSN Search!
>>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfeeŽ
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] Server side question !!!
Posted by Anne Thomas Manes <at...@gmail.com>.
Axis supports C/C++. Given that you've been using LEIF, I assume that
your services are written in C/C++. Do you intend to rewrite all your
apps?
Axis for Java can run in any servlet engine -- including any J2EE
server. It's true that Sun's J2EE server includes a SOAP engine, but
it doesn't support C/C++. Assuming that you really don't want to
reimplement all your apps, Axis provides you with a common SOAP
architecture that supports both Java and C++.
Anne
On 7/6/06, Luis Rivera <lu...@hotmail.com> wrote:
>
> Hi axis users,
>
> I finally got the green light to port the server side or our web services
> from LEIF/Roguewave to axis. The main reason is economics, we want to
> explore cheaper options.
>
> I was exploring the alternatives for serverlet containers in the server
> side, which will be Windows/Solaris. I think the best for axis is Tomcat,
> but I am confused with regard to the version I am supposed to use or if this
> is the way to go.
>
> I also looked into Sun Application Server (J2EE based I believe) but why
> would I do that? It seems that I would not need axis if I used Sun
> Application Server.
>
> So, if I had to justify axis/Tomcat vs J2EE, what would be the best
> arguments in favor of axis?
>
> Thanks in advance,
> --Luis R.
>
> _________________________________________________________________
> Don't just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org