Hi John,

I think I was confused by this call

fAssertions.put("Description-1001".intern(), 
                new AssertionInfo(new Description1001(), 
DescriptionElement.class, null));

Should this instead be

Description1001 d1001 = new Description1001();
fAssertions.put(d1001.getAssertionId(), 
                new AssertionInfo(d1001, DescriptionElement.class, null));

My initial thinking was that assertion classes may not map 1 to 1 with 
assertion ids. If assertions are similar or the same an adopter may 
implement one assertion class and register it for multiple assertion ids.

Thoughts?

Lawrence 





John Kaputin <[EMAIL PROTECTED]> 
02/13/2008 05:24 AM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: Use of getAssertionId method






Lawrence,
The 'registerAssertion' method originally proposed on the wiki was:
registerAssertion(IAssertion assertion, String id, String dependencies);

where 'id' was the assertion id, specified separately to the assertion 
itself.

I thought it would be better to encapsulate this inside the assertion 
object, so I added the getAssertionID() method to the Assertion interface 
and changed the register method signature to:
registerAssertion(Assertion assertion, Class target, String dependencies)

Note, this signature no longer has a String parameter for specifying the 
'id'. It's encapsulated in the Assertion class and accessed by the 
frameword via the getAssertionID() method.  This places responsibility for 

specifying the Assertion ID correctly on the Assertion implementor, not on 

the caller of the ExtensionRegistry.registerAssertion method (this might 
be the same person, but it's not gauranteed).

regards,
John Kaputin




Lawrence Mandel <[EMAIL PROTECTED]> 
13/02/2008 02:24
Please respond to
[email protected]


To
[email protected]
cc

Subject
Use of getAssertionId method






Hi John,

I implemented assertion Interface-1009 (committed to branch Woden62) to 
test out the work that you've done with the validation framework. Can you 
tell me what is the purpose of the getAssertionId method? It looks like 
the framework already has the assertion id as it's specified when the 
assertion is registered. Who makes use of this method?

Thanks,

Lawrence



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to