aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Nuttall (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ARIES-810) Invalid filter string in blueprint.xml results in a non-obvious error
Date Wed, 18 Jan 2012 15:26:41 GMT
Invalid filter string in blueprint.xml results in a non-obvious error
---------------------------------------------------------------------

                 Key: ARIES-810
                 URL: https://issues.apache.org/jira/browse/ARIES-810
             Project: Aries
          Issue Type: Bug
          Components: Application
            Reporter: Mark Nuttall
            Assignee: Mark Nuttall
            Priority: Minor


If a developer specifies an incorrect filter string within their blueprint xml, the error
reported doesn't make it obvious that this is the case.

For example:

<reference id="WorldRef" interface="com.acme.World" filter="osgi.jndi.service.name=dupCheck/topLevelSequencer"></reference>

This should read (notice the brackets):

<reference id="WorldRef" interface="com.acme.World" filter="(osgi.jndi.service.name=dupCheck/topLevelSequencer)"></reference>

This results in ImportedServiceImpl throwing an unhelpful InvalidAttributeException. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message