It should work as long as you don't try to use any kind of transform
with a document view.  This requires the use of
HttpServletResponseWrapper, which is a Servlet 2.3 thing.

Unfortunately all the sample web applications currently do exactly this,
and friendbook uses HttpServletRequest.getParameterMap() which also is a
2.3 thing.

If you don't try to use some of the advanced features, Maverick should
work fine with the 2.2 spec.  If it doesn't, post something here and
we'll probably be able to fix it :-)

Jeff Schnitzer
[EMAIL PROTECTED]

> >  -----Original Message-----
> > From:       Haseltine, Celeste
> > Sent:       Friday, March 08, 2002 1:31 PM
> > To: '[EMAIL PROTECTED]'
> > Subject:    Maverick and JRUN Server 3.1
> >
> > I'm new to the list, and I did not find a means of searching the
> archives
> > for this question, so forgive me if this has been asked and answered
> > before.
> >
> > Has anyone used Maverick with JRUN Server 3.1?  I've looked at using
> > Struts in my next project, but Struts is so tightly coupled with the
> > Jakarta tag libraries that I am unable to separate the MVC
architecture
> > portions for the non-MVC architecture portions easily.  JRUN Server
has
> a
> > very nice set of JSP tag libraries, including SQL and form tag
libraries,
> > and a nice interface that I can use to define a JDBC datasource with
> > connection pooling, and JNDI lookup capabilities.  I would prefer to
use
> > the JSP tag libraries and the other features that JRUN Server gives
me,
> > but I don't see an easy way to this with Struts.
> >
> > I did note that the current version of Maverick is based on Sun
Servlet
> > standard 2.3, where as the current version of JRUN is still based on
> > Servlet standard 2.2 (the next version of JRUN is due out late this
> > summer).  Would I be able to easily modify the segments of  Maverick
> that
> > utilize the servlet standard 2.3 to make it "backwards compatible"
with
> > 2.2?  Or am I better off just writing my own MVC container around
JRUN's
> > features/Tag Library?  I would prefer to use a tried, true and
tested
> MVC
> > architecture if I can, vs writing my own around JRUN's tag libraries
and
> > other features.
> >
> > Thanks in advance for any advice/recommendations from those of you
> > familiar with Maverick.
> >
> > Celeste Haseltine, PE
> >
> >
> >
> 
> _______________________________________________
> Mav-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/mav-user

_______________________________________________
Mav-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mav-user

Reply via email to