I'm working on a tapestry documentation generator and I would like to use
Tapestry's built-in specification parser for it.
My generator already works for specification files (a simple XML parser) but
suddenly annotations were added which makes my life more difficult. If
possible then I would use Tapestry's parser for parsing the libraries and
components which of course handles annotations as well.
The concrete problem is: when I start the registry and try to access the
methods of ISpecificationSource, I get an exception that the
"infrastructure" is not initialized yet. When I tried to initialize the
"infrastructure" I saw that it uses servlet specific services/objects.
So I decided to ask you developers that: is it worth trying to start the
registry outside a servlet container OR I should implement my own annotation
"parsing".
Of course Tapestry's parser would be a more integrated and robust
solution...
Thanks,
Norbi
----- Original Message -----
From: "Howard Lewis Ship" <[EMAIL PROTECTED]>
To: "Tapestry development" <[email protected]>
Sent: Wednesday, August 03, 2005 8:00 PM
Subject: Re: start tap. registry
The code for starting up the Registry is pretty simple; it's inside
ApplicationServlet.
The nature of HiveMind is that the services will generally be
instantiated/configured in a just-in-time fashion. You will have to
do a lot of mocking up of the Servlet API, I think. It would be
eaiser if you could describe your goals.
On 8/3/05, Norbert Sándor <[EMAIL PROTECTED]> wrote:
Hello,
Is there a way to start the tapestry services outside of a servlet
container?
I'm working on tapdoc and I wanted to check if it is possible to use the
parser and annotation support of tapestry instead of implementing my own.
BR,
Norbi
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
