Thanks for your interests in the pluto admin portlet.
On 2/19/06, Patrick Huber <[EMAIL PROTECTED]
> wrote:
Yes. Currently we are planning to support tomcat and jetty.
IMHO, auto-generation of context.xml is preferred. The admin portlet
should be able to deploy a *standard* portlet app. All container-specific
configurations (such as tomcat's META-INF/context.xml) should be
auto-generated or configurable via the admin portlet interface.
Having some sort of web service is a good idea, but i don't have much
experience on that... i will take a look at that if i have time.
I was already thinking a bit about deployment and we'd probably have
to have some servlet-container-specific code for each servlet
container we want to support.
Yes. Currently we are planning to support tomcat and jetty.
Do you think it makes sense to let the deployer enter a context name
or should we just assume the deployer already includes a
META-INF/context.xml? I don't know but that file may be
servlet-container-specific too...
IMHO, auto-generation of context.xml is preferred. The admin portlet
should be able to deploy a *standard* portlet app. All container-specific
configurations (such as tomcat's META-INF/context.xml) should be
auto-generated or configurable via the admin portlet interface.
For the web-service, we could do all the work in a servlet and use a
portlet as thin frontend. Everything the Portlet does, is dispatching
the request to the servlet.
Having some sort of web service is a good idea, but i don't have much
experience on that... i will take a look at that if i have time.
Patrick
--
"I love deadlines. I like the whooshing sound they make as they fly
by." -- Douglas Adams
As for introducing some additional dependencies (such as SpringPortlet)
into pluto, IMHO, we should make sure that:
1/ We are not using some early-access libs, since they may be unstable.
2/ We are using some libs that are re-distributable under the apache license.
Check the maven 2 repository ( http://repo1.maven.org/maven2/ ) to make
sure that the lib is available from there... otherwise, building pluto will require
that users download the lib and put into their local repo manually.
3/ We use some dependencies because we need them to avoid re-inventing
the wheel... So, before implementing something, we'd better ask ourselves
if using a certain dependency can really save our time and make our code
simpler...
Thanks again for all your help!
Regards.
--
ZHENG Zhong
- http://heavyz.blogspot.com/
- http://people.apache.org/~zheng/
