[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jetspeed-user
Subject:    Best Practices for developing portlets...
From:       David Allen <dallen () rapidigm ! com>
Date:       2001-12-20 17:34:41
[Download RAW message or body]


I am just beginning to ramp up on development with JetSpeed and was
wondering if someone could describe their preferred method of developing in
this environment?

The cycle seems to be code->compile->create par->deploy->test which seems a
bit cumbersome. Is it possible to short circuit this process in a meaningful
way... i.e. code->compile->test by directly writing class files to the
appropriate directories? This seems to work, but only with a manual restart
of the webapp. Any suggestions on how to simplify this?

Making sense of what gets deployed where is also a bit of a concern. Is it
possible to simple deploy a par file with the portlet.xml and have the
actual portlet implementation classes deployed in the WEB-INF/classes
directory? This would simplify the deployment of multiple portlets which all
access a common object model.

Any suggestions would be greatly appreciated.

Thanks,

David Allen


[prev in list] [next in list] [prev in thread] [next in thread]