Ah, saw the new doc.
So you don't see any actual need for more than one application servlet, not
that I have thought of a situation where you would want it.
In terms of wrapping db transaction and security filters, you just make sure
they are put before the tapestry filter ?
What about when you have other servlets in the app, will Tapestry coexist
and not add extra processing time?
Henrik
----- Original Message -----
From: "Howard Lewis Ship" <[EMAIL PROTECTED]>
To: "Tapestry development" <[email protected]>
Sent: Thursday, August 31, 2006 11:37 PM
Subject: Re: Thoughts on Tap5 .application
Yes, it's a cool idea, in terms of doing an "end run" around the
limitations
of web.xml.
On 8/30/06, James Carman <[EMAIL PROTECTED]> wrote:
So, you went with the TapestryFilter idea? Cool! :-)
> I'm looking to keep the amount in the web.xml minimal.
>
> You configure the TapestryFilter (good idea James!) and tell Tapestry
> about
> your root package and it takes it from there.
>
> I've been documenting as I got but can't post the docs from my laptop,
> details when I get home to the desktop tomorrow.
>
> On 8/30/06, devel - Fashion Content <[EMAIL PROTECTED]> wrote:
>>
>> I've been brewing on how general app config might work in Tap5
>>
>> web.xml is a fairly rigid structure and backwards compatibility has
>> limits
>> it's use previously,
>> but given the reliance on Java5, I think it is fair to require a
>> recent
>> servlet spec. The main
>> benefit of web.xml as I see it is that most Java server-side
>> developers
>> know
>> web.xml already.
>>
>> Currently any non-trivial Tap4 app requires web.xml,
>> webapp.applicationand
>> hivemodule.xml
>> I assume the intention is to change .application to a structure more
>> like
>> hivemodule.xml and use
>> it as a common configuration file for the application, but I think it
>> would
>> be nice if more things
>> could be derived/defaulted based on web.xml
>>
>> <servlet-name> is used for the .application name and page/template
path.
>> Could we used it
>> to determine the class package name? I 'com.example.app' a legal name?
>> Should the page/template
>> path then be WEB-INF/com/example/app or WEB-INF/com.example.app?
either?
>> Or
>> only
>> one to make tooling easy?
>>
>> ServletFilter/Listeners are webapp wide. I use one to identify the
>> user/user-agent, but the interface
>> with the ApplicationServlet seems slightly bothersome.
>> Currently there is a Registry per appservlet. Is that actually needed?
>> Isn't
>> it likely that you would want
>> to share objects between the registries? I recall getting stuck on
>> iterating
>> the registries as I couldnt
>> get a list of the servlet names.
>>
>> If multiple registries are indeed needed, how would you configure a
>> common
>> registry containing services
>> that can be wired and accessed through the individual servlet
>> registry?
>>
>> I have a couple of other ideas, but what do you think about these?
>>
>> Henrik
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Howard M. Lewis Ship
> TWD Consulting, Inc.
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Apache HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
James Carman, President
Carman Consulting, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
