Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <2119879157.1138219509491.JavaMail.jira@ajax.apache.org>
Date: Wed, 25 Jan 2006 21:05:09 +0100 (CET)
From: "Aaron Mulder (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-1450) Console usage plans use old
 namspace & parentId
In-Reply-To: <1454353075.1136952140137.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-1450?page=comments#action_12363994 ] 

Aaron Mulder commented on GERONIMO-1450:
----------------------------------------

I'm not convinced that we want to encourage people to use the new config ID format for their own stuff -- at least until we resolve the version issue.  And specifically relating to the patch, a user's application is not a CAR so we definitely wouldn't want to recommend they use a /car URI.  But the easiest solution is just to omit the parentId.  :)

> Console usage plans use old namspace & parentId
> -----------------------------------------------
>
>          Key: GERONIMO-1450
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1450
>      Project: Geronimo
>         Type: Bug
>   Components: console, documentation
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Critical
>      Fix For: 1.0.1, 1.1
>  Attachments: GERONIMO-1450.patch
>
> The usage pages in the console show deployment plans, and the namespaces in those deployment plans don't have version numbers in them.  It's not disastrous as we should convert those, but it'd be much better to fix them.
> Also, they have the wrong (o/a/g/Server) parentId, which is disastrous.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira