I wanted to offer a complete "module" made of several controllers, the views
(JSPs), resource bundles and such. Like packaging a flow of Spring Webflow.
But in the end that would impose a hefty burden on the client app as the
appearance probably won't match and all that (menus et al). So finally I'm
more inclined to include all the components (as tag files) and some sample
JSPs. Not as feature complete but much easier (for me) and probably offering
a better overall integration. JSPs would offer the best solution for a
complete (self-contained) web app (helping for example with page navigation)
but may be not for something that is just included as a subset of
functionality in a bigger scheme.
On Tue, Sep 16, 2008 at 2:33 AM, <glassfish_at_javadesktop.org> wrote:
> > Hi,
> >
> > So I'm
> > going with an alternative route using tag
> > handlers/files wich are very easy
> > to package and can pretty much do the same in a
> > portable way.
>
> That's...curious.
>
> What exactly were you trying to do?
>
> I'm just puzzled because while, yes, tag files can be bundled in a jar
> file, that's about the only advantage over JSPs.
>
> Most folks want to bundle pre-compiled JSP to a) speed up start up or b)
> hide the JSP source code.
>
> A tag file jar (AFAIK) achieves neither of these.
>
> So, I'm just curious what your use case is.
> [Message sent by forum member 'whartung' (whartung)]
>
> http://forums.java.net/jive/thread.jspa?messageID=299472
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>