[gatein-issues] [JBoss JIRA] Updated: (GTNWSRP-228) Upgrade Chromattic to 1.1.0-beta5

[ https://issues.jboss.org/browse/GTNWSRP-228?page=com.atlassian.jira.plugi... ] Julien Viet updated GTNWSRP-228: -------------------------------- Description: The most important change that should affect WSRP usage of Chromattic in 1.1.0-beta5 is @Properties annotation behavior change. Previously it was exposing any property of the node and now it exposes only a property that is a residual property (denoted by * as name). In particular jcr meta property such as jcr:uuid or jcr:primaryType will not be exposed anymore. The other change is the addition of the @Naming annotation to work also with @Properties to specify a namespace so a map accessor annotated with @Naming("foo") @Properties exposes foo:* matching properties but Chromattic takes care of the prefix so doing a put("bar", "juu") will actually create a "foo:bar" = "juu" property in the JCR node. So I think that WSRP should be OK and could even simplify the code by removing the necessary filtering that was performed with the propertiesBlackList in the RegistrationPropertiesMapping and MappedMap classes. was:The most important change that should affect WSRP usage of Chromattic in 1.1.0-beta5 is @Properties annotation behavior change. Previously it was exposing any property of the node and now it exposes only a property that is a residual property (denoted by * as name). In particular jcr meta property such as jcr:uuid or jcr:primaryType will not be exposed anymore. The other change is the addition of the @Naming annotation to work also with @Properties to specify a namespace so a map accessor annotated with @Naming("foo") @Properties exposes foo:* matching properties but Chromattic takes care of the prefix so doing a put("bar", "juu") will actually create a "foo:bar" = "juu" property in the JCR node. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira