You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/08/24 12:23:30 UTC
[jira] Created: (JCR-1086) JCR2SPI: Workspace.getImportHandler
creates a handler which doesn't work properly under JDK 1.4.
JCR2SPI: Workspace.getImportHandler creates a handler which doesn't work properly under JDK 1.4.
------------------------------------------------------------------------------------------------
Key: JCR-1086
URL: https://issues.apache.org/jira/browse/JCR-1086
Project: Jackrabbit
Issue Type: Bug
Components: SPI
Reporter: Julian Reschke
JCR2SPI returns an import handler which delegates work to a SAXTransformerHandler. In JDK, that one has a known issue not processing namespace prefix mappings properly (will attach a separate test case).
Proposals:
- drop JDK 1.4 support
- tune the JCR2SPI handler to create namespace attributes when needed
- use an entirely different serializer
My personal preference would be just to drop JDK 1.4 support, but that may not be acceptable for everyone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1086) JCR2SPI: Workspace.getImportHandler
creates a handler which doesn't work properly under JDK 1.4.
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-1086:
------------------------
Fix Version/s: 1.4
> JCR2SPI: Workspace.getImportHandler creates a handler which doesn't work properly under JDK 1.4.
> ------------------------------------------------------------------------------------------------
>
> Key: JCR-1086
> URL: https://issues.apache.org/jira/browse/JCR-1086
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Assignee: angela
> Fix For: 1.4
>
> Attachments: TransformerHandlerTest.java
>
>
> JCR2SPI returns an import handler which delegates work to a SAXTransformerHandler. In JDK, that one has a known issue not processing namespace prefix mappings properly (will attach a separate test case).
> Proposals:
> - drop JDK 1.4 support
> - tune the JCR2SPI handler to create namespace attributes when needed
> - use an entirely different serializer
> My personal preference would be just to drop JDK 1.4 support, but that may not be acceptable for everyone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JCR-1086) JCR2SPI: Workspace.getImportHandler
creates a handler which doesn't work properly under JDK 1.4.
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela reassigned JCR-1086:
---------------------------
Assignee: angela
> JCR2SPI: Workspace.getImportHandler creates a handler which doesn't work properly under JDK 1.4.
> ------------------------------------------------------------------------------------------------
>
> Key: JCR-1086
> URL: https://issues.apache.org/jira/browse/JCR-1086
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Assignee: angela
> Attachments: TransformerHandlerTest.java
>
>
> JCR2SPI returns an import handler which delegates work to a SAXTransformerHandler. In JDK, that one has a known issue not processing namespace prefix mappings properly (will attach a separate test case).
> Proposals:
> - drop JDK 1.4 support
> - tune the JCR2SPI handler to create namespace attributes when needed
> - use an entirely different serializer
> My personal preference would be just to drop JDK 1.4 support, but that may not be acceptable for everyone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1086) JCR2SPI: Workspace.getImportHandler
creates a handler which doesn't work properly under JDK 1.4.
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-1086.
-------------------------
Resolution: Fixed
> JCR2SPI: Workspace.getImportHandler creates a handler which doesn't work properly under JDK 1.4.
> ------------------------------------------------------------------------------------------------
>
> Key: JCR-1086
> URL: https://issues.apache.org/jira/browse/JCR-1086
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Assignee: angela
> Fix For: 1.4
>
> Attachments: TransformerHandlerTest.java
>
>
> JCR2SPI returns an import handler which delegates work to a SAXTransformerHandler. In JDK, that one has a known issue not processing namespace prefix mappings properly (will attach a separate test case).
> Proposals:
> - drop JDK 1.4 support
> - tune the JCR2SPI handler to create namespace attributes when needed
> - use an entirely different serializer
> My personal preference would be just to drop JDK 1.4 support, but that may not be acceptable for everyone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1086) JCR2SPI: Workspace.getImportHandler
creates a handler which doesn't work properly under JDK 1.4.
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated JCR-1086:
--------------------------------
Attachment: TransformerHandlerTest.java
Standalone test case illustrating the problem.
> JCR2SPI: Workspace.getImportHandler creates a handler which doesn't work properly under JDK 1.4.
> ------------------------------------------------------------------------------------------------
>
> Key: JCR-1086
> URL: https://issues.apache.org/jira/browse/JCR-1086
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Attachments: TransformerHandlerTest.java
>
>
> JCR2SPI returns an import handler which delegates work to a SAXTransformerHandler. In JDK, that one has a known issue not processing namespace prefix mappings properly (will attach a separate test case).
> Proposals:
> - drop JDK 1.4 support
> - tune the JCR2SPI handler to create namespace attributes when needed
> - use an entirely different serializer
> My personal preference would be just to drop JDK 1.4 support, but that may not be acceptable for everyone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1086) JCR2SPI: Workspace.getImportHandler
creates a handler which doesn't work properly under JDK 1.4.
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522474 ]
Julian Reschke commented on JCR-1086:
-------------------------------------
Forgot one proposal:
- install a newer version of JAXP on top of JDK 1.4 (the JDK 1.5 JAXP is available as an upgrade for JDK 1.4)
> JCR2SPI: Workspace.getImportHandler creates a handler which doesn't work properly under JDK 1.4.
> ------------------------------------------------------------------------------------------------
>
> Key: JCR-1086
> URL: https://issues.apache.org/jira/browse/JCR-1086
> Project: Jackrabbit
> Issue Type: Bug
> Components: SPI
> Reporter: Julian Reschke
> Attachments: TransformerHandlerTest.java
>
>
> JCR2SPI returns an import handler which delegates work to a SAXTransformerHandler. In JDK, that one has a known issue not processing namespace prefix mappings properly (will attach a separate test case).
> Proposals:
> - drop JDK 1.4 support
> - tune the JCR2SPI handler to create namespace attributes when needed
> - use an entirely different serializer
> My personal preference would be just to drop JDK 1.4 support, but that may not be acceptable for everyone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.