> Is org.apache.struts.axis4struts ok for a package?
This may not be as simple as it seems. If the requirements are:
- Some code will be required to be used in Struts apps
- Some code will be required to be used in Axis apps
- It would be nice to have a single JAR file that could be deployed in
both Axis and Struts
- Having a single Jar with both Axis and Struts code may be a requirement
if we are going to maintain release levels.
If these are acceptable, then it may be better to have:
org.axis4struts
with Struts code in
org.axis4struts.struts...
and Axis code in
org.axis4struts.axis...
Then there may be room for utilities/common classes to be in
org.axis4struts.other.package.names...
I have a feeling that in the end attempting to get code to be accepted in
to the cvs repositories of BOTH Axis and Struts (let alone maintaining
release levels in two repositories) may be a pain (or impossible). This may
be a creature that may have to live life outside both. Especially
considering that Axis and Struts have releases that are independent of each
other.
Anyone else have thoughts on this?
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
