Morris [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 4:59 PM
To: [EMAIL PROTECTED]
Subject: RE: [AXIS4STRUTS] The old In and Out
Hal and others,
I agree with your analysis, however I think there is still some
synergy.
First, loading presentation directly from a Web service could
I can see the appeal of exposing the web application's code as web
services
using Axis. It seems like exposing Action classes directly as web
services
will be more trouble than it's worth. It would seem better to move the
code
in the Action class into another class (not tied to Struts/Web)
[mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 9:22 AM
To: 'Struts Developers List'
Subject: RE: [AXIS4STRUTS] The old In and Out
I am used to dealing with EJBs so I am probably not as sympathetic as I
should have been to people that have written web applications without
EJBs.
In a sense
If we start with the idea [Kevin's suggestion] that on the Axis side we
develop a Web Service that accepts SOAP Requests with an XML payload and
spins that payload into an HTTP POST/GET to a Struts Application as if
that POST or GET was coming from a Web Browser. Then we need not make
any changes
Mike -
If we start with the idea [Kevin's suggestion] that on the Axis side we
develop a Web Service that accepts SOAP Requests with an XML payload and
spins that payload into an HTTP POST/GET to a Struts Application as if
that POST or GET was coming from a Web Browser. Then we need not
] [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 11:54 AM
To: Struts Developers List
Cc: [EMAIL PROTECTED]
Subject: Re: [AXIS4STRUTS] The old In and Out
Mike -
If we start with the idea [Kevin's suggestion] that on the Axis side
we
develop a Web Service that accepts SOAP Requests
Developers List
Cc: [EMAIL PROTECTED]
Subject: Re: [AXIS4STRUTS] The old In and Out
Mike -
If we start with the idea [Kevin's suggestion] that on the
Axis side we
develop a Web Service that accepts SOAP Requests with an
XML payload and
spins that payload into an HTTP POST/GET to a Struts
benefit to combining them.
Hal
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 1:54 PM
To: Struts Developers List
Cc: [EMAIL PROTECTED]
Subject: Re: [AXIS4STRUTS] The old In and Out
Mike -
If we start
*FridayModeOn*
Axis and Struts, like ice cream and sex, are both good things, but I
don't
see much benefit to combining them.
I think it depends on the flavor of the Ice Cream... ;-)
*FridayModeOff*
Is the idea behind Axis for Struts to expose Action classes as Web
Services?
Yes.
] The old In and Out
*FridayModeOn*
Axis and Struts, like ice cream and sex, are both good things, but I
don't
see much benefit to combining them.
I think it depends on the flavor of the Ice Cream... ;-)
*FridayModeOff*
Is the idea behind Axis for Struts to expose Action classes as Web
I still haven't really absorbed the rationale for this, and my
difficulty in answering some of your questions make me willing to
step up and say so.
Maybe it would help if we could frame the goal of the project, in
terms of more than wouldn't it be cool?
How about:
My understanding
Hal and others,
I agree with your analysis, however I think there is still some
synergy.
First, loading presentation directly from a Web service could be useful
although this could be exposed directly through a custom tag so is
really not that helpful. Re-encoding a SOAP request to match the
, 2003 1:24 PM
To: [EMAIL PROTECTED]
Subject: RE: [AXIS4STRUTS] The old In and Out
I think Axis4Struts is a cool idea, but... there are some viability
issues to address, IMO.
I just implemented a web services project using access and thought about
the MVC model of Struts, and if that could
At 4:49 PM -0500 2003/01/24, [EMAIL PROTECTED] wrote:
I still haven't really absorbed the rationale for this, and my
difficulty in answering some of your questions make me willing to
step up and say so.
Maybe it would help if we could frame the goal of the project, in
terms of more than
] The old In and Out
Hal and others,
I agree with your analysis, however I think there is still some
synergy.
First, loading presentation directly from a Web service could be useful
although this could be exposed directly through a custom tag so is
really not that helpful. Re-encoding a SOAP request
True. But somehow, to leverage what struts really is, you would need to
communicate some kind of instructions from the server side controller.
I think the core of what I am saying is that Axis does *not* provide a
view. And therefore you would have controller functions on the other
side of the
Michael,
There is very little difference. Others have mentioned support for
multiple view, which is great but I don't want to have to do double
the effort to support two views instead of one. There is benefit in
defining that response in a view neutral way so that interaction could
be between
True. But somehow, to leverage what struts really is, you would need to
communicate some kind of instructions from the server side controller.
The idea is to have the SOAP request contain essentially the same data as
would be in an HTTP post (or get). Then you invoke Struts Actions the same
] The old In and Out
At 4:49 PM -0500 2003/01/24, [EMAIL PROTECTED] wrote:
I still haven't really absorbed the rationale for this, and my
difficulty in answering some of your questions make me willing to
step up and say so.
Maybe it would help if we could frame the goal of the project
] The old In and Out
** You may find more utility in creating set of client side proxys for
Struts server side controller contructs. In other words, RPC the
selected controller components. ActionForms would be user defined,
but
the ActionForward, ActionErrors, etc ... could be proxy
: Benjamin Tomasini [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 3:23 PM
To: Struts Developers List
Subject: RE: [AXIS4STRUTS] The old In and Out
Thanks...
I think the interaction with Flash, et. al. could be a big deal.
[Mike Oliver] Me thinks you think I think Axis4Struts will become
-
From: David Morris [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 4:01 PM
To: [EMAIL PROTECTED]
Subject: RE: [AXIS4STRUTS] The old In and Out
Michael,
There is very little difference. Others have mentioned support for
multiple view, which is great but I don't want to have to do
Subject: RE: [AXIS4STRUTS] The old In and Out
True. But somehow, to leverage what struts really is, you would need to
communicate some kind of instructions from the server side controller.
I think the core of what I am saying is that Axis does *not* provide a
view. And therefore you would
.
Michael Oliver
AppsAsPeers LLC
7391 S. Bullrider Ave.
Tucson, AZ 85747
Phone:(520)574-1150
Fax:(520)844-1036
-Original Message-
From: Benjamin Tomasini [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 7:36 PM
To: Struts Developers List
Subject: RE: [AXIS4STRUTS] The old In and Out
: Benjamin Tomasini [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 7:36 PM
To: Struts Developers List
Subject: RE: [AXIS4STRUTS] The old In and Out
I don't mean to sound overly negative. I think the idea is interesting,
and am looking forward to seeing creative solutions to some
-1150
Fax:(520)844-1036
-Original Message-
From: Benjamin Tomasini [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 7:36 PM
To: Struts Developers List
Subject: RE: [AXIS4STRUTS] The old In and Out
I don't mean to sound overly negative. I think the idea is interesting
Developers List
Subject: RE: [AXIS4STRUTS] The old In and Out
I don't mean to sound overly negative. I think the idea is interesting,
and am looking forward to seeing creative solutions to some of these
issues. :)
I could be missing the point. Most of my comments are from an XML-RPC
perspective
List
Subject: RE: [AXIS4STRUTS] The old In and Out
On Fri, 2003-01-24 at 22:41, Mike Oliver wrote:
Oh and BTW I believe you are taking a too narrow view of VIEW, so at
least on that point we disagree. I would define view as the
presentation layer as you do, but the consumer dictates what
28 matches
Mail list logo
