Bug 780408 (SOA-2839) - It's possible to unregister a namespace used in a nodetype definition.
Summary: It's possible to unregister a namespace used in a nodetype definition.
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-2839
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-24 14:22 UTC by Marek Baluch
Modified: 2011-01-24 16:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-24 16:26:16 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2839 0 None None None Never

Description Marek Baluch 2011-01-24 14:22:42 UTC 
project_key: SOA

See linked issue.
Comment 1 Marek Baluch 2011-01-24 14:23:04 UTC 
Link: Added: This issue depends MODE-1084
Comment 2 Randall Hauch 2011-01-24 16:02:52 UTC 
As mentioned on MODE-1084:

Strictly speaking, the specification says it's possible to unregister a namespace that is already used. You can even re-register it with a different prefix, either at the session level (i.e., the mapping is local only to that session), or at the workspace level (the remapping appears for everyone). 

Of course in ModeShape, you have to have the correct privileges in order to unregister or register namespaces. 

So, this is not a defect. I'll leave it opened so we can discuss questions/comments/concerns, but this (as with MODE-1084) will eventually be closed as 'Rejected'.
Comment 3 Randall Hauch 2011-01-24 16:26:16 UTC 
As noted in the comments, this is not a defect, but is actually allowed by the JCR specifications. Therefore, rejecting.
Note You need to log in before you can comment on or make changes to this bug.