[infinispan-issues] [JBoss JIRA] Commented: (ISPN-948) Support XML marshaling of Configuration instances

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587948#comment-12587948 ] 

Galder Zamarreño commented on ISPN-948:
---------------------------------------

Jurgen, thanks very much once again but I can't apply your patch cos lines don't match the master branch:

{code}Failed to apply patch for file core/src/main/java/org/infinispan/config/GlobalConfiguration.java: Context mismatch. Expected line:
      protected Long distributedSyncTimeout = 240000L; // default
Found line:
      @ConfigurationDoc(name="distributedSyncTimeout",{code}

Once again, I'd suggest you open an account in GitHub (it's very easy :)) ) and follow the process of forking our repo, creating a topic branch for your work, synching to the latest (with the linked scripts) and then request a pull. This process makes contributions and their integrations a lot simpler both for you and I. See http://community.jboss.org/docs/DOC-16089

> Support XML marshaling of Configuration instances
> -------------------------------------------------
>
>                 Key: ISPN-948
>                 URL: https://issues.jboss.org/browse/ISPN-948
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Configuration
>    Affects Versions: 4.2.1.CR3
>            Reporter: Jürgen Kellerer
>            Assignee: Manik Surtani
>             Fix For: 5.0.0.Final
>
>         Attachments: Feature_ISPN-948_Support_XML_marshaling_of_Configuration_instances.patch, Feature__ISPN-948__Support_XML_marshaling_of_Configuration_instances.patch, ISPN-948-Final.patch
>
>   Original Estimate: 4 hours
>          Time Spent: 4 hours
>  Remaining Estimate: 0 minutes
>
> Infinispan supports a very flexible way of configuring caches using multiple levels of inheritance. 
> While this is really nice, it is sometimes not easy to understand how exactly a particular cache was configured. 
> (E.g. JPA is just one example where a cache configuration can be adjusted in several ways).
> JMX or debuggers help but may not always be available.
> What about allowing to convert a configuration instance back to XML to give a quick overview of the really applied settings. _(Optionally it might also be a nice little feature to implement a "toXmlString();" method or override the default and also make this available through JMX)_
> JAXB annotations are already present on all configurable options but a couple getters and a @XmlRootElement annotation is missing that would allow to convert an existing instance back to XML. The effort in doing this should be rather low.
> ---
> This feature request may also fit with #ISPN-791 as it would allow to transfer cache configs using XML.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira