[
https://issues.jboss.org/browse/ISPN-1214?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1214:
----------------------------------------
The solution was much simpler. There was no need to move the @XmlElement element from the
private method to the public one. Simply adding a @XmlTransient to the public setter would
have worked and that fixes both config doc generation while the test still works.
Btw, I'm adding a commented line to config doc mvn plugin so that developers can
figure out how to debug issues like this. It's a matter of adding some java ops so
that the javadoc process can be traced with a remote debugger.
Configuration.getCacheLoaders still not working as expected
-----------------------------------------------------------
Key: ISPN-1214
URL:
https://issues.jboss.org/browse/ISPN-1214
Project: Infinispan
Issue Type: Bug
Components: Configuration, Loaders and Stores
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
To get around the issues in ISPN-1161, programmatic and XML configuration methods were
separated.
The solution used generated issues with the config generation as shown in
https://github.com/infinispan/infinispan/pull/402#issuecomment-1483390
The latest solution has in turn resulted in a regression in
https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/96/#sh...
for
XmlFileParsingTest/org_infinispan_config_parsing_XmlFileParsingTest_testConfigurationMergingJaxb
So, provide a solution that solves both tests and works w/ configuration doc generation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira