You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2013/01/09 11:44:12 UTC

[jira] [Created] (STANBOL-881) (Re)add the String only Constructor to the PosTag class

Rupert Westenthaler created STANBOL-881:
-------------------------------------------

             Summary: (Re)add the String only Constructor to the PosTag class
                 Key: STANBOL-881
                 URL: https://issues.apache.org/jira/browse/STANBOL-881
             Project: Stanbol
          Issue Type: Bug
            Reporter: Rupert Westenthaler
            Assignee: Rupert Westenthaler
            Priority: Minor


This was removed because the "PosTag(String tag, LexicalCategory...lc)" also allowd to create unmapped (tag only) instances.

However this is only true for java source code. When using the reflection API it is not possible to obtain an string only constructor. because of that the call to 

    PosTag.class.getConstructor(String.class)

results in a "NoSuchMethodException: org.apache.stanbol.enhancer.nlp.pos.PosTag.<init>(java.lang.String)".

An example of an component that tires to obtain the string only constructor of PosTag is the "CeliTagSetRegistry". Because of that it encounters a

Caused by: java.lang.NoSuchMethodException: org.apache.stanbol.enhancer.nlp.pos.PosTag.<init>(java.lang.String)
	at java.lang.Class.getConstructor0(Class.java:2706)
	at java.lang.Class.getConstructor(Class.java:1657)
	at org.apache.stanbol.enhancer.engines.celi.CeliTagSetRegistry.getTag(CeliTagSetRegistry.java:354)

This was not discovered until Jenkins build #1208 because all POS tags used by CELI where actually predefined in the mappings defined by the registry. However (most likely) due to an server side change of the CELI server this is no longer the case - causing the registry to create an ad-hoc PosTag for the unknown mapping and therefore throwing this exception


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira