[ 
http://issues.apache.org/jira/browse/GERONIMO-2284?page=comments#action_12427910
 ] 
            
Aaron Mulder commented on GERONIMO-2284:
----------------------------------------

Unfortunately, I'm not sure that's realistic given where we are.  We currently 
hide the group/artifact/version/type from the user, and the name they specify 
becomes the artifact, with a fixed group, version, and type.  Because of that, 
I dont' think we can accept slashes in the name.

However, be aware that the point of this issue is to alter the artifact name, 
which is separate from the DB pool name.   When mapping a resource ref you only 
need the DB pool name (which can be "Daytrader" or "DaytraderJDBC" just not 
"jdbc/Daytrader"), and for your dependency you can just list 
artifact=DaytraderJDBC or whatever.

So, bottom line, the user should be able to stay unaware of whatever we use as 
the group name (curently console.dbpool), but the artifact name can't have 
slashes, so the DB pool name most likely can't have slashes.

If it was really desirable we could have an "advanced options" screen to let 
the user override the group/artifact/version/type so they could leave slashes 
in the pool name and override the module ID to be something valid, but I don't 
think this adds a whole lot of value.  They can already generate the plan and 
just add a "jdbc/" to the pool name in the plan.

> Console DB/JMS and Security Realm naming inconsistent
> -----------------------------------------------------
>
>                 Key: GERONIMO-2284
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2284
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>             Fix For: 1.1.x
>
>
> When the console creates a database connection pool or JMS resource, the 
> module ID has the group "console.dbpool" or "console.jms".  However, when it 
> creates a security realm, the module ID just has the group "console" and the 
> artifact ID has the prefix "realm-".  Instead, the security realm module ID 
> should have the group "console.realm" and the artifact ID should be the same 
> as the name the user specified.

-- 
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

        

Reply via email to