[opencms-dev] Modules vs WEB-INF/lib/

[Jonathan Woods]

Modules generally also provide configuration information about themselves in
<opencms home>/WEB-INF/config/opencms-modules.xml.  This information can
include the definition of module metadata (e.g. author, title) and (more
interestingly) new resource types.  Modules also generally contain JSPs to
provide module-specific views; and they may also provide XSD schemas for
their own resource types.

When you're developing a module, it's quite possible to put module stuff
into the VFS by hand; and provided that you have the right entries in
opencms-modules.xml, it will be exactly as if you managed the module via the
Workplace.  Either way, you soon want to get to a position in which
uploading/refreshing your module is as automated as possible, unless you are
a very much better coder than I am!  The DevShell class I posted is one way
of achieving this, and it could certainly be improved upon.

Jon

-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Mike McGrath
Sent: 19 June 2006 14:38
To: The OpenCms mailing list
Subject: [opencms-dev] Modules vs WEB-INF/lib/

What's the difference between creating a module and loading it through the
module interface and creating a jar and dropping it in opencms/WEB-INF/lib/?


    -Mike

_______________________________________________
This mail is sent to you from the opencms-dev mailing list To change your
list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev