[XDoclet-JIRA] Updated: (XDT-1493) allow superior packages as general package substitution target

The following issue has been updated:

    Updater: Frank Wildenhain (mailto:[email protected])
       Date: Fri, 5 Aug 2005 9:31 AM
    Comment:
concrete solution proposal (successfully tested with generation of ejb interfaces, data objects and value objects)
    Changes:
             Attachment changed to concrete_solution_proposal.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1493?page=history

---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1493

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-1493
    Summary: allow superior packages as general package substitution target
       Type: Improvement

     Status: Open
   Priority: Minor

 Original Estimate: 1 day
 Time Spent: Unknown
  Remaining: 1 day

    Project: XDoclet
 Components: 
             Core
             EJB Module
   Versions:
             1.2.3
             1.3

   Assignee: xdoclet-devel (Use for new issues)
   Reporter: Frank Wildenhain

    Created: Fri, 5 Aug 2005 9:23 AM
    Updated: Fri, 5 Aug 2005 9:31 AM

Description:
Currently the ejbdoclet element "packagetagshandler.packagesubstitution"
allows only to substitute a package with a concrete substitute package name.

An important improvement would be to allow to substitute a package with it's superior package too.

Special packages for interfaces (and technological package names in general respectively) are often not wanted.


Example:
A package "~.mail.impl" should be substituted with package "~.mail".
And a package "~.address.impl" should be substituted with package "~.address".

Currently this is already possible but only via two concrete successive calls with the attribute sets
{packages="mail.impl",substituteWith="mail"} and 
{packages="address.impl",substituteWith="address"}.

A general solution should be possible so that not all existent
combinations of superior package and subpackage has to be specified.

Possible solution:
Support the empty string in the packagesubstitution attribute "substituteWith".
An empty string signals that the target package is the superior package of the package to be substituted.




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf