[jira] Commented: (COCOON-2148) SourceProtocolHandler causes NPE

2007-11-26 Thread Andreas Hartmann (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545359
 ] 

Andreas Hartmann commented on COCOON-2148:
--

Grzegorz, thanks for your comment!

I also have the feeling that the patch is rather a workaround. I'll try if 
Batik 1.7 Beta1 behaves differently, and I'll try to provide a test case.

I'm not sure if C2.2 is affected since I don't use it yet, but I can give it a 
try.

 SourceProtocolHandler causes NPE
 

 Key: COCOON-2148
 URL: https://issues.apache.org/jira/browse/COCOON-2148
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Batik
Affects Versions: 2.1.11-dev (Current SVN)
Reporter: Andreas Hartmann
 Attachments: patch-issue2148.txt


 I used an action to pass the current source resolver to the 
 SourceProtocolHandler, but this resulted in an NPE because the URI of the 
 TranscoderInput object was null. After I applied a little patch to the 
 SourceProtocolHandler which enabled the fallback to the default handler if 
 the URL to resolve is null, it worked. 

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



[jira] Commented: (COCOON-2148) SourceProtocolHandler causes NPE

2007-11-26 Thread Andreas Hartmann (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545377
 ] 

Andreas Hartmann commented on COCOON-2148:
--

The ParsedURLDefaultProtocolHandler of Batik 1.6 handles null values for urlStr 
explicitely:

ParsedURLDefaultProtocolHandler:parseURL(String):87


ParsedURLData ret = constructParsedURLData();

if (urlStr == null) return ret;


 SourceProtocolHandler causes NPE
 

 Key: COCOON-2148
 URL: https://issues.apache.org/jira/browse/COCOON-2148
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Batik
Affects Versions: 2.1.11-dev (Current SVN)
Reporter: Andreas Hartmann
 Attachments: patch-issue2148.txt


 I used an action to pass the current source resolver to the 
 SourceProtocolHandler, but this resulted in an NPE because the URI of the 
 TranscoderInput object was null. After I applied a little patch to the 
 SourceProtocolHandler which enabled the fallback to the default handler if 
 the URL to resolve is null, it worked. 

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



[jira] Commented: (COCOON-2148) SourceProtocolHandler causes NPE

2007-11-26 Thread Andreas Hartmann (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545394
 ] 

Andreas Hartmann commented on COCOON-2148:
--

The SVGSerializer fails with Batik 1.7 beta 1 because 
SAXDocumentFactory.startElement() now contains a block which depends on the 
parser (which is not initialized and causes an NPE):


if (inProlog) {
inProlog = false;
try {
isStandalone = parser.getFeature
(http://xml.org/sax/features/is-standalone;);
} catch (SAXNotRecognizedException ex) {
}
try {
xmlVersion = (String) parser.getProperty
(http://xml.org/sax/properties/document-xml-version;);
} catch (SAXNotRecognizedException ex) {
}
}


 SourceProtocolHandler causes NPE
 

 Key: COCOON-2148
 URL: https://issues.apache.org/jira/browse/COCOON-2148
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Batik
Affects Versions: 2.1.11-dev (Current SVN)
Reporter: Andreas Hartmann
 Attachments: patch-issue2148.txt


 I used an action to pass the current source resolver to the 
 SourceProtocolHandler, but this resulted in an NPE because the URI of the 
 TranscoderInput object was null. After I applied a little patch to the 
 SourceProtocolHandler which enabled the fallback to the default handler if 
 the URL to resolve is null, it worked. 

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



[jira] Commented: (COCOON-2148) SourceProtocolHandler causes NPE

2007-11-26 Thread Andreas Hartmann (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545410
 ] 

Andreas Hartmann commented on COCOON-2148:
--

I contacted Sylvain off-list, I hope he knows more.

 SourceProtocolHandler causes NPE
 

 Key: COCOON-2148
 URL: https://issues.apache.org/jira/browse/COCOON-2148
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Batik
Affects Versions: 2.1.11-dev (Current SVN)
Reporter: Andreas Hartmann
 Attachments: patch-issue2148.txt


 I used an action to pass the current source resolver to the 
 SourceProtocolHandler, but this resulted in an NPE because the URI of the 
 TranscoderInput object was null. After I applied a little patch to the 
 SourceProtocolHandler which enabled the fallback to the default handler if 
 the URL to resolve is null, it worked. 

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



[jira] Commented: (COCOON-2148) SourceProtocolHandler causes NPE

2007-11-26 Thread Andreas Hartmann (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545417
 ] 

Andreas Hartmann commented on COCOON-2148:
--

I sent a mail to the Batik users list:

http://www.nabble.com/Handling-null-parameters-in-ParsedURLProtocolHandler.parseURL%28String%29-tf4874770.html

 SourceProtocolHandler causes NPE
 

 Key: COCOON-2148
 URL: https://issues.apache.org/jira/browse/COCOON-2148
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Batik
Affects Versions: 2.1.11-dev (Current SVN)
Reporter: Andreas Hartmann
 Attachments: patch-issue2148.txt


 I used an action to pass the current source resolver to the 
 SourceProtocolHandler, but this resulted in an NPE because the URI of the 
 TranscoderInput object was null. After I applied a little patch to the 
 SourceProtocolHandler which enabled the fallback to the default handler if 
 the URL to resolve is null, it worked. 

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



[jira] Commented: (COCOON-2148) SourceProtocolHandler causes NPE

2007-11-25 Thread Grzegorz Kossakowski (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545272
 ] 

Grzegorz Kossakowski commented on COCOON-2148:
--

Thanks for providing this patch Andreas.

Even though, I would like to commit it I must admit I don't fully understand 
what's the problem and how this patch fixes it as I don't know guts of Batik. 
Anyway, if you are really sure that it's not going to break anything I would be 
happy to accept it.

Is Batik block in C2.2 affected by this problem?

 SourceProtocolHandler causes NPE
 

 Key: COCOON-2148
 URL: https://issues.apache.org/jira/browse/COCOON-2148
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Batik
Affects Versions: 2.1.11-dev (Current SVN)
Reporter: Andreas Hartmann
 Attachments: patch-issue2148.txt


 I used an action to pass the current source resolver to the 
 SourceProtocolHandler, but this resulted in an NPE because the URI of the 
 TranscoderInput object was null. After I applied a little patch to the 
 SourceProtocolHandler which enabled the fallback to the default handler if 
 the URL to resolve is null, it worked. 

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