Hi All,
We have developed a huge Turbine Application from which we would like to expose
some action methods as webservices. After thinking a lot I came to a conclusion
that this could be done by just analyzing the public methods of actions, and
just select which ones you want and which you
PROTECTED]
Subject: Exposing Methods in Actions as WebServices
Hi All,
We have developed a huge Turbine Application from which we would like to
expose
some action methods as webservices. After thinking a lot I came to a
conclusion
that this could be done by just analyzing the public methods
according to IoC.. The components shouldn't need a rundata or a velocity or
anything..
Eric
-Original Message-
From: Jürgen Hoffmann [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 9:38 AM
To: [EMAIL PROTECTED]
Subject: Exposing Methods in Actions as WebServices
Hi All
-
Von: Eric Pugh [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. Dezember 2003 11:24
An: 'Turbine Developers List'
Betreff: RE: Exposing Methods in Actions as WebServices
Something to think about is that if you write your action methods as just a
thin wrapper around your actual buissnes logic
later, or supply some sort of SOAP session
Oron
-Original Message-
From: Jürgen Hoffmann [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 10:37 AM
To: 'Turbine Developers List'
Cc: 'Akmal Sarhan'
Subject: AW: Exposing Methods in Actions as WebServices
Hi Oron and Eric,
Thanks
We've done something very similar and very simple ( IMO ). We wanted
some processing to be executed remotely from a old, mainframe type
system. So we knew ( and had done ) this processing within java on
our app server. We just created an action that performed that
process, and RunData provided
