[Design the new POJO MicroContainer] - Re: Case sensitivity in injecting a bean's property
by scott.stark@jboss.org
I noted the issue between bean and mbean property case a while ago:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92469
so I'm surprised this is a regression. I don't know why it would have worked because even though the correct case ala java beans for a setPort/getPort is port (based on java.beans.Introspector behavior/javadoc), jmx 1.2, page 40 states:
anonymous wrote :
| Case Sensitivity
| All attribute and operation names derived from these design patterns are casesensitive.
| For example, this means that the methods getstate and setState
| define two attributes, one called state that is read-only, and one called State that
| is write-only.
|
| While case sensitivity applies directly to component names of standard MBeans, it is
| also applicable to all component names of all types of MBeans, standard or dynamic.
| In general, all names of classes, attributes, operations, methods, and internal
| elements defined in the JMX specification are case sensitive, whether they appear as
| data or as functional code when they are manipulated by management operations.
|
so there are conflicting naming conventions. All I can see that we do is to allow a property matching strictness setting that can be specified when referencing a bean property that would relax the case sensitivity issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004963#4004963
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004963
19 years, 2 months
[Design of JBossCache] - Re: Last minute 2.0 API suggestions
by genman
The Collection interface has a "boolean remove(Object k)", and it's nice (when writing adaptors, see that other thread) to see if the remove operation actually worked.
One good thing about the Collection interfaces is that they always return information. This suggests that all Node methods should return something. Some thoughts:
| NodeSPI -
| void setVersion(DataVersion version); - Return replaced version?
| void removeChildrenDirect(); - Return count of children removed?
| void removeChildDirect(Fqn fqn); - boolean true if removed?
| void removeChildDirect(Object childName); - ""
| Cache -
| void removeNode(Fqn fqn); - boolean true if removed
| void evict(Fqn fqn, boolean recursive); - ""
|
I also wonder if Cache.getVersion() shouldn't return a Version (not String) object instead? Version might implement a "before" method as well. It'd be nice for people writing something like this:
Cache c;
if (c.getVersion().before(Version.XYZ))
throw new Exception("Cache not >= Version XYZ");
I'm not sure how often this use case comes up, though.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004944#4004944
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004944
19 years, 2 months