You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Andrew Cornwall (JIRA)" <ji...@apache.org> on 2007/07/24 21:56:31 UTC
[jira] Created: (HARMONY-4528) Signature mismatches in jndi code
Signature mismatches in jndi code
---------------------------------
Key: HARMONY-4528
URL: https://issues.apache.org/jira/browse/HARMONY-4528
Project: Harmony
Issue Type: Bug
Components: Classlib
Environment: Winx86 build 558789
Reporter: Andrew Cornwall
Priority: Minor
Some methods in JNDI code have different signatures than the Sun implementation. They are:
javax.naming.NameParser:
- public Name parse(String s) throws InvalidNameException, NamingException; - should just throw NamingException
javax.naming.spi.DirectoryManager:
- public static Object getObjectInstance(Object o, Name n, Context c, Hashtable<?, ?> h, Attributes a) throws NamingException, Exception - should just throw Exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-4528) Signature mismatches in jndi code
Posted by "Paulex Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paulex Yang resolved HARMONY-4528.
----------------------------------
Resolution: Fixed
Regis, patch applied at r559308, thanks a lot.
Andrew, please verify this patch is fixed as you expected, thanks.
> Signature mismatches in jndi code
> ---------------------------------
>
> Key: HARMONY-4528
> URL: https://issues.apache.org/jira/browse/HARMONY-4528
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: Winx86 build 558789
> Reporter: Andrew Cornwall
> Assignee: Paulex Yang
> Priority: Minor
> Attachments: Harmony-4528.diff
>
>
> Some methods in JNDI code have different signatures than the Sun implementation. They are:
> javax.naming.NameParser:
> - public Name parse(String s) throws InvalidNameException, NamingException; - should just throw NamingException
> javax.naming.spi.DirectoryManager:
> - public static Object getObjectInstance(Object o, Name n, Context c, Hashtable<?, ?> h, Attributes a) throws NamingException, Exception - should just throw Exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-4528) Signature mismatches in jndi code
Posted by "Paulex Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paulex Yang reassigned HARMONY-4528:
------------------------------------
Assignee: Paulex Yang
> Signature mismatches in jndi code
> ---------------------------------
>
> Key: HARMONY-4528
> URL: https://issues.apache.org/jira/browse/HARMONY-4528
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: Winx86 build 558789
> Reporter: Andrew Cornwall
> Assignee: Paulex Yang
> Priority: Minor
> Attachments: Harmony-4528.diff
>
>
> Some methods in JNDI code have different signatures than the Sun implementation. They are:
> javax.naming.NameParser:
> - public Name parse(String s) throws InvalidNameException, NamingException; - should just throw NamingException
> javax.naming.spi.DirectoryManager:
> - public static Object getObjectInstance(Object o, Name n, Context c, Hashtable<?, ?> h, Attributes a) throws NamingException, Exception - should just throw Exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4528) Signature mismatches in jndi code
Posted by "Regis Xu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Regis Xu updated HARMONY-4528:
------------------------------
Attachment: Harmony-4528.diff
this patch modify the signature to be compatible with spec, May somebody pls try it?
> Signature mismatches in jndi code
> ---------------------------------
>
> Key: HARMONY-4528
> URL: https://issues.apache.org/jira/browse/HARMONY-4528
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: Winx86 build 558789
> Reporter: Andrew Cornwall
> Priority: Minor
> Attachments: Harmony-4528.diff
>
>
> Some methods in JNDI code have different signatures than the Sun implementation. They are:
> javax.naming.NameParser:
> - public Name parse(String s) throws InvalidNameException, NamingException; - should just throw NamingException
> javax.naming.spi.DirectoryManager:
> - public static Object getObjectInstance(Object o, Name n, Context c, Hashtable<?, ?> h, Attributes a) throws NamingException, Exception - should just throw Exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (HARMONY-4528) Signature mismatches in jndi code
Posted by "Mark Hindess (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Hindess closed HARMONY-4528.
---------------------------------
Closing as the signatures look correct in the current code.
> Signature mismatches in jndi code
> ---------------------------------
>
> Key: HARMONY-4528
> URL: https://issues.apache.org/jira/browse/HARMONY-4528
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: Winx86 build 558789
> Reporter: Andrew Cornwall
> Assignee: Paulex Yang
> Priority: Minor
> Attachments: Harmony-4528.diff
>
>
> Some methods in JNDI code have different signatures than the Sun implementation. They are:
> javax.naming.NameParser:
> - public Name parse(String s) throws InvalidNameException, NamingException; - should just throw NamingException
> javax.naming.spi.DirectoryManager:
> - public static Object getObjectInstance(Object o, Name n, Context c, Hashtable<?, ?> h, Attributes a) throws NamingException, Exception - should just throw Exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.