[jira] Commented: (JCR-888) javax.jcr.NamespaceException: : is not a registered namespace uri

2008-04-02 Thread Dave Erickson (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584658#action_12584658
 ] 

Dave Erickson commented on JCR-888:
---

Hi,

Yes, it was the IBM JVM that was causing the problem.  I was actually 
using jackrabbit inside Lotus Expeditor.  The solution was to switch out 
the JVM for the SUN one.

Dave Erickson
Sr. IT Specialist
Software Services for Lotus
IBM Software Group
Cell: 858-472-3293
Email: [EMAIL PROTECTED]




From:
Rohnny Moland (JIRA) [EMAIL PROTECTED]
To:
[EMAIL PROTECTED]
Date:
04/01/2008 12:34 PM
Subject:
[jira] Commented: (JCR-888) javax.jcr.NamespaceException: : is not a 
registered namespace uri




[ 
https://issues.apache.org/jira/browse/JCR-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584266#action_12584266
 
] 

Rohnny Moland commented on JCR-888:
---

I assume that Dave got this exception when using the ibm vm. Is that 
right, Dave?

We have the same problem when we try to deploy jackrabbit to websphere 
application server with ibm vm. The problem is that ibm and sun have 
different interpretations of what a properties file can contain. With sun 
vm it is legal to have an empty key, but with ibm vm this is not allowed. 
When jackrabbit tries to load the ns_reg.properties and ns_idx.properties 
files from disk, the ibm vm fails with the exception over because if 
contains something like =1. See 
org.apache.jackrabbit.NamespaceRegistryImpl.load(). The easy fix is just 
to add the empty name space to the map after loading the properties file, 
which is included in a patch. 

I hope this can be included in the next version of jackrabbit-core.


created successfully the first time it is run.  Subsequent attempts to 
login result in a javax.jcr.NamespaceException.
registered namespace uri.
org.apache.jackrabbit.core.NamespaceRegistryImpl.getPrefix(NamespaceRegistryImpl.java:538)
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.checkNamespace(NodeTypeRegistry.java:1292)
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.validateNodeTypeDef(NodeTypeRegistry.java:1415)
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.internalRegister(NodeTypeRegistry.java:1221)
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.init(NodeTypeRegistry.java:671)
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.create(NodeTypeRegistry.java:118)
org.apache.jackrabbit.core.RepositoryImpl.createNodeTypeRegistry(RepositoryImpl.java:571)
org.apache.jackrabbit.core.RepositoryImpl.init(RepositoryImpl.java:262)
org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584)
org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:245)
org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:265)
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:333)
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:388)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.





 javax.jcr.NamespaceException: : is not a registered namespace uri
 -

 Key: JCR-888
 URL: https://issues.apache.org/jira/browse/JCR-888
 Project: Jackrabbit
  Issue Type: Bug
  Components: jackrabbit-core
Affects Versions: 1.2.3, 1.3
 Environment: Windows XP, Eclipse 3.1, JRE 1.4.2 and 5.0
Reporter: Dave Erickson
 Attachments: NamespaceRegistryImpl.java.patch


 Using the first hops with both versions 1.2.3 and 1.3, the repository is 
 created successfully the first time it is run.  Subsequent attempts to login 
 result in a javax.jcr.NamespaceException.
 DEBUG - Initializing transient repository
 INFO - Starting repository...
 INFO - LocalFileSystem initialized at path repository\repository
 Exception in thread main javax.jcr.NamespaceException: : is not a 
 registered namespace uri.
   at 
 org.apache.jackrabbit.core.NamespaceRegistryImpl.getPrefix(NamespaceRegistryImpl.java:538)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.checkNamespace(NodeTypeRegistry.java:1292)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.validateNodeTypeDef(NodeTypeRegistry.java:1415)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.internalRegister(NodeTypeRegistry.java:1221)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.init(NodeTypeRegistry.java:671)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.create(NodeTypeRegistry.java:118)
   at 
 org.apache.jackrabbit.core.RepositoryImpl.createNodeTypeRegistry(RepositoryImpl.java:571)
   at 
 org.apache.jackrabbit.core.RepositoryImpl.init(RepositoryImpl.java:262)
   at 
 

[jira] Commented: (JCR-888) javax.jcr.NamespaceException: : is not a registered namespace uri

2007-04-26 Thread Dave Erickson (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492011
 ] 

Dave Erickson commented on JCR-888:
---

Thanks for the quick response.  I found out that the issue was due to a custom 
JRE.  When I used the default 1.4.2 and 5.0 JRE's from Sun, there is no longer 
an issue.  I will close this ticket.

 javax.jcr.NamespaceException: : is not a registered namespace uri
 -

 Key: JCR-888
 URL: https://issues.apache.org/jira/browse/JCR-888
 Project: Jackrabbit
  Issue Type: Bug
  Components: core
Affects Versions: 1.2.3, 1.3
 Environment: Windows XP, Eclipse 3.1, JRE 1.4.2 and 5.0
Reporter: Dave Erickson

 Using the first hops with both versions 1.2.3 and 1.3, the repository is 
 created successfully the first time it is run.  Subsequent attempts to login 
 result in a javax.jcr.NamespaceException.
 DEBUG - Initializing transient repository
 INFO - Starting repository...
 INFO - LocalFileSystem initialized at path repository\repository
 Exception in thread main javax.jcr.NamespaceException: : is not a 
 registered namespace uri.
   at 
 org.apache.jackrabbit.core.NamespaceRegistryImpl.getPrefix(NamespaceRegistryImpl.java:538)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.checkNamespace(NodeTypeRegistry.java:1292)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.validateNodeTypeDef(NodeTypeRegistry.java:1415)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.internalRegister(NodeTypeRegistry.java:1221)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.init(NodeTypeRegistry.java:671)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.create(NodeTypeRegistry.java:118)
   at 
 org.apache.jackrabbit.core.RepositoryImpl.createNodeTypeRegistry(RepositoryImpl.java:571)
   at 
 org.apache.jackrabbit.core.RepositoryImpl.init(RepositoryImpl.java:262)
   at 
 org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584)
   at 
 org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:245)
   at 
 org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:265)
   at 
 org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:333)
   at 
 org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:388)
   at testing.FirstHops.main(FirstHops.java:24)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Closed: (JCR-888) javax.jcr.NamespaceException: : is not a registered namespace uri

2007-04-26 Thread Dave Erickson (JIRA)

 [ 
https://issues.apache.org/jira/browse/JCR-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Erickson closed JCR-888.
-

Resolution: Fixed

This does not occur when the default 1.4.2_11 and 5.0 JRE's are used.  It was 
only happening when using a custom JRE

 javax.jcr.NamespaceException: : is not a registered namespace uri
 -

 Key: JCR-888
 URL: https://issues.apache.org/jira/browse/JCR-888
 Project: Jackrabbit
  Issue Type: Bug
  Components: core
Affects Versions: 1.2.3, 1.3
 Environment: Windows XP, Eclipse 3.1, JRE 1.4.2 and 5.0
Reporter: Dave Erickson

 Using the first hops with both versions 1.2.3 and 1.3, the repository is 
 created successfully the first time it is run.  Subsequent attempts to login 
 result in a javax.jcr.NamespaceException.
 DEBUG - Initializing transient repository
 INFO - Starting repository...
 INFO - LocalFileSystem initialized at path repository\repository
 Exception in thread main javax.jcr.NamespaceException: : is not a 
 registered namespace uri.
   at 
 org.apache.jackrabbit.core.NamespaceRegistryImpl.getPrefix(NamespaceRegistryImpl.java:538)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.checkNamespace(NodeTypeRegistry.java:1292)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.validateNodeTypeDef(NodeTypeRegistry.java:1415)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.internalRegister(NodeTypeRegistry.java:1221)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.init(NodeTypeRegistry.java:671)
   at 
 org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.create(NodeTypeRegistry.java:118)
   at 
 org.apache.jackrabbit.core.RepositoryImpl.createNodeTypeRegistry(RepositoryImpl.java:571)
   at 
 org.apache.jackrabbit.core.RepositoryImpl.init(RepositoryImpl.java:262)
   at 
 org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584)
   at 
 org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:245)
   at 
 org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:265)
   at 
 org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:333)
   at 
 org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:388)
   at testing.FirstHops.main(FirstHops.java:24)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (JCR-888) javax.jcr.NamespaceException: : is not a registered namespace uri

2007-04-25 Thread Dave Erickson (JIRA)
javax.jcr.NamespaceException: : is not a registered namespace uri
-

 Key: JCR-888
 URL: https://issues.apache.org/jira/browse/JCR-888
 Project: Jackrabbit
  Issue Type: Bug
  Components: core
Affects Versions: 1.3, 1.2.3
 Environment: Windows XP, Eclipse 3.1, JRE 1.4.2 and 5.0
Reporter: Dave Erickson


Using the first hops with both versions 1.2.3 and 1.3, the repository is 
created successfully the first time it is run.  Subsequent attempts to login 
result in a javax.jcr.NamespaceException.


DEBUG - Initializing transient repository
INFO - Starting repository...
INFO - LocalFileSystem initialized at path repository\repository
Exception in thread main javax.jcr.NamespaceException: : is not a registered 
namespace uri.
at 
org.apache.jackrabbit.core.NamespaceRegistryImpl.getPrefix(NamespaceRegistryImpl.java:538)
at 
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.checkNamespace(NodeTypeRegistry.java:1292)
at 
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.validateNodeTypeDef(NodeTypeRegistry.java:1415)
at 
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.internalRegister(NodeTypeRegistry.java:1221)
at 
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.init(NodeTypeRegistry.java:671)
at 
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.create(NodeTypeRegistry.java:118)
at 
org.apache.jackrabbit.core.RepositoryImpl.createNodeTypeRegistry(RepositoryImpl.java:571)
at 
org.apache.jackrabbit.core.RepositoryImpl.init(RepositoryImpl.java:262)
at 
org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584)
at 
org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:245)
at 
org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:265)
at 
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:333)
at 
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:388)
at testing.FirstHops.main(FirstHops.java:24)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.