Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
Grzegorz Kossakowski wrote:
This brings us to couple of questions:
1. Do we want to have a policy to have only one base package (e.g.
o.a.c.servletservice.*) per one module (artifact, JAR, you name it)?
2. What OSGi folks can say about this situation? I remember that
there was some requirement to have clean package structure in order
to run in OSGi environment easily but I'm not expert in this area.
There shouldn't be two different artifacts *exporting* the same
package, which means having classes intendet to be used by other
artifacts in this package. That's afaik the only requirement for OSGi.
This can be easily reached if a block uses o.a.c.{blockname} for its
own packages.
So do you think we need to rename o.a.c.callstack into
o.a.c.servletservice.callstack ?
IMO, no. It doesn't violate the rule that there shouldn't be two
different artifacts exporting the same package.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair [EMAIL PROTECTED]
________________________________________________________________________
