So I have been researching using JSP from within JSDK 2.0. Basically
without RequestDispatcher ( .include() ) any attempt would be a very
kludgy proposal.
We should add support for JSP within JSDK 2.1/Jakarta though.
My solution for using JSP or other Servlets *without* Turbine is to
think of it as an API as well. Specifically so that custom Actions and
Screens can be used in legacy applications but share code with modern
applications.
The basic way to do this is to use Action.build() as a component from
within our JSP. The problem is that we need to convince Turbine that it
is running in an exceptable env. The best way to do this is to have a
RunData factory within Turbine.java
Within Turbine.java:
public RunData getRunData(HttpServletRequest req, HttpServletResponse
res);
The current Turbine.goGet() would simply call Turbine.getRunData and
continue operations. This is only a minor modification as it involves
moving the current tested code into another method within Turbine.java
I have to do this within my local application but I believe this is best
for Turbine in general. It would open it up to a much larger audience.
Thoughts?
--
Kevin A Burton
Senior Software Engineer
Kendara Inc
http://www.kendara.com
Mobile: 408-910-6145
Linux - You *will* be assimilated
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
