[ http://issues.apache.org/jira/browse/COCOON-1861?page=all ]
Antonio Gallardo updated COCOON-1861: ------------------------------------- Did you tested the patch? I have few questions: 1- What happens when the uri is null? I am asking because code code will call: super.startElement(uri, name, raw, attributes); 2- What happens when this element end? Because the element must emit and endElement call defined in line 795: endElement(String uri, String name, String raw) Can be in this case uri == null? If yes, do we need a similar fix? > Check for Null URI in LDAPTransformer > ------------------------------------- > > Key: COCOON-1861 > URL: http://issues.apache.org/jira/browse/COCOON-1861 > Project: Cocoon > Type: Bug > Components: Blocks: Naming > Versions: 2.1.8, 2.1.9 > Reporter: Igor Naumov > Assignee: Antonio Gallardo > Priority: Minor > > In the LDAPTransformer.java > (src\blocks\naming\java\org\apache\cocoon\transformation\LDAPTransformer.java) > the URI is not checked for NULL. > On some J2EE servers (SAP NetWeaver) the URI passed may be NULL and it causes > a NullPointerException. > A simple fix is to add a check for NULL URI and just pass through that > element: > public void startElement(String uri, String name, String raw, Attributes > attributes) throws SAXException { > + if (uri == null) { > + super.startElement(uri, name, raw, attributes); > + return; > + } > if (!uri.equals(my_uri)) { > super.startElement(uri, name, raw, attributes); > return; -- 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
