axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Galbreath, Mark A" <Galbreat...@state.gov>
Subject RE: Project from hell?
Date Fri, 14 May 2004 20:34:36 GMT
wow...finally...some validation!

Of course, the real trick is going to be calling the applet classes from a
servlet and be able to handle the method args.

Mark

-----Original Message-----
From: Davanum Srinivas [mailto:davanum@gmail.com]
Sent: Friday, May 14, 2004 4:12 PM
To: axis-user@ws.apache.org
Subject: Re: Project from hell?


No. You are on the right track :)

-- dims

On Fri, 14 May 2004 16:05:58 -0400, Galbreath, Mark A
<galbreathma@state.gov> wrote:
> 
> so...you feel my pain....
> 
> My idea is to remove the applet functionality to a Struts framework.  The
> framework would handle the back-and-forth between the client and the Web
> service.
> 
> Am I being too simplistic?
> 
> Personally, I think I have been given an impossible task.
> 
> Mark
> 
> 
> 
> -----Original Message-----
> From: Dennis Sosnoski [mailto:dms@sosnoski.com]
> Sent: Friday, May 14, 2004 3:54 PM
> To: axis-user@ws.apache.org
> Subject: Re: Project from hell?
> 
> Galbreath, Mark A wrote:
> 
> >EXACTOMUDO!  :-(
> >
> >-----Original Message-----
> >From: Sherman, Dennis (END-CHI) [mailto:dennis.sherman@endinfosys.com]
> >Sent: Friday, May 14, 2004 9:12 AM
> >
> >Your task sounds to me suspiciously like someone at an executive level
> >having heard about web services, and thinking they've found the silver
> >bullet to all their problems.
> >
> >
> Then you've got two choices I'd see as reasonable. The first is to use
> an actual web service, with the clients converted from applets to
> standalone applications (perhaps deployed using JWS, a great solution).
> You could use JMS or SMTP for the actual web services, to get the
> queuing advantages you said were important. This should let you preserve
> much of the UI and avoid a total rewrite.
> 
> The second alternative is to either modify your existing applet-based
> code or design a pure HTML approach that talks to servlets, with the
> servlets implementing queuing behind the scenes. I don't know how much
> this would help with your basic problems, though.
> 
> Using an applet based frontend for web services is possible, but really
> only makes sense if you've already got a web service that you just want
> to access from the applet - I really wouldn't recommend this as an
> up-front design.
> 
>   - Dennis
> 
> --
> Dennis M. Sosnoski
> Enterprise Java, XML, and Web Services
> Training and Consulting
> http://www.sosnoski.com
> Redmond, WA  425.885.7197
> 
> 
>

Mime
View raw message