search

sshyran / genxdm

Automatically exported from code.google.com/p/genxdm
0 stars 0 forks source link

NodeFactory methods createAttribute and createElement say "not null" for prefix parameter, but this isn't enforced by bridges #66

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Discussion about this issue arose from this thread:

https://groups.google.com/group/genxdm/browse_thread/thread/2077af30d2762369

Boiling down the discussion as of this filing, options are:

a) Do nothing, and let bridges fail however they wish.

b) Require bridges to do a "non-null" check.

c) Treat null as equivalent to ""

d) Treat null as equivalent to "assign it for me."

Original issue reported on code.google.com by eric%tib...@gtempaccount.com on 21 Jun 2011 at 5:46

GoogleCodeExporter commented 8 years ago 
Make consistent prior to 1.0 release.

Original comment by aale...@gmail.com on 26 Jul 2012 at 7:22

GoogleCodeExporter commented 8 years ago 
Based on the discussion, to which I add this: I do not think "c" is 
"acceptable", the only remaining "acceptable" option is b, which is the way the 
contract is written anyway. So we'll do the "easy" thing and make bridges meet 
the contract as specified.

Original comment by aale...@gmail.com on 30 Jul 2012 at 7:39

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r345.

Original comment by aale...@gmail.com on 30 Jul 2012 at 7:44