Jorg Heymans ha scritto: > Stefano Bagnara wrote: >> [...] >> As I have had this problem in past [1] for some of them, I suggest to >> simply remove the schema declaration from the xinfo. >> So any: >> <block> >> <version>1.0</version> >> <schema-type>#something#</schema-type> >> </block> >> Will be >> <block> >> <version>1.0</version> >> </block> >> >> This happens, to me, at least for this files: >> DefaultDataSourceSelector.xinfo >> DefaultSocketManager.xinfo >> DefaultThreadManager.xinfo >> ResourceLimitingThreadManager.xinfo >> [...] > > Is this change potentially backwards incompatible ? I'm not using the > cornerstone libs so i can't really judge its impact.
Well, removing the schema declaration simply avoid checks. So the backward incompatibility is there only if you add schema declarations, not if you remove them. Of course you are removing details, but I think not too much people is using them anymore as EXLBR-30 is there since almost 2 years and no one else complained but me, and current 2.2.1 (online since february) artifacts do not work in xinfo based frameworks, and again no one complained but me ;-) I guess very few people is using this xinfo and in our last JAMES Server release we shipped patched cornerstone datasource and cornerstone sockets impl because of bad schema validation in official 2.1 jars. > If the other developers agree i will apply your patch and we can do > another release. Thank you!! Stefano > Thanks, > Jorg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
