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" <[EMAIL PROTECTED]>
>Reply-To: [email protected]
>To: [email protected]
>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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
_________________________________________________________________
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
