cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: package names? additional jar dependencies?
Date Mon, 12 Aug 2002 10:26:43 GMT

> -----Original Message-----
> From: Conal Tuohy []
> Sent: Sunday, August 11, 2002 9:20 AM
> To: Cocoon Developers (E-mail)
> Subject: package names? additional jar dependencies?
> I've written some components for dealing with javamail stores: MailSource
> and MailSourceFactory, and a few associated (helper) classes which will
> probably also include an XMLizer when I factor out the XMLizing code. I'd
> like to commit them to the scratchpad, but first I want to know
> the correct
> location for my package. There are a lot of Sources in the
> org.apache.cocoon.components.source.impl package, but it seemed to me
> preferable to put my classes in a package of their own, where they can be
> package-private, for instance.
> org.apache.cocoon.mail ? (this is what I'm using at present)
> org.apache.cocoon.components.mail ?
> org.apache.cocoon.components.source.impl.mail ?

If your implementing consists only of a source then I think the third
package name is the best to use. I would discourage you from using
the first as optional components do not belong to the top-level.
If you have additional components for mail handling the second one
would be fine.

> Also, these components require some extra jars; namely activation.jar (the
> Java Activation Framework) and mail.jar (JavaMail). How do I indicate this
> dependency?
This dependency is indicated in the build.xml ant build script. We can't add
(AFAIK) the jars to Cocoon directly because of the Sun licence. Check the
build script and you will find a class test if the mail.jar is available
and see some optional compilation for some mail components.

BTW what does your source do? Reading from an email account and sending
emails (=WritableSource)?


To unsubscribe, e-mail:
For additional commands, email:

View raw message