aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Nuttall (JIRA)" <j...@apache.org>
Subject [jira] Created: (ARIES-138) Give useful feedback when service registration listener callback matching fails
Date Tue, 02 Feb 2010 16:26:28 GMT
Give useful feedback when service registration listener callback matching fails
-------------------------------------------------------------------------------

                 Key: ARIES-138
                 URL: https://issues.apache.org/jira/browse/ARIES-138
             Project: Aries
          Issue Type: Improvement
          Components: Blueprint
    Affects Versions: Incubation
            Reporter: Mark Nuttall
            Priority: Minor


As a blueprint managed application developer, I'd like some helpful feedback when things aren't
working quite as I'd expect. For example, service and service registration listener callback
methods "must have a signature matching with the following format":

	public void anyMethodName (ServiceType serviceInstance, Map serviceProperties)
	
A programmer might well attempt to register a callback method with signature (ServiceType,
HashMap) or (ServiceType, Properties) which will not be called: ServiceRegistrationListener.getSignatureType()
is strict on demanding 'Map' as the second parameter type. This is correct, but for a certain
level of debug, we could certainly output a message indicating that method signature matching
had failed, or that various candidate methods had been rejected. 

The general requirement here is for programmers to be able to debug their blueprint applications
without recourse to the source code :-)

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


Mime
View raw message