Hi Holger, "Holger Hoffstaette" <[email protected]> wrote on 06/10/2010 04:37:17 PM:
> First of all thanks for the interest, all. Apologies for not answering > earlier, got pulled away.. > > On Thu, 03 Jun 2010 00:38:49 -0400, Michael Glavassevich wrote: > > I did commit a bug fix today, but we really are trying to get a build and > > testing done right now, along with the remaining doc updates. Khaled did > > Understood. > > > propose another release for later in the year, so perhaps OSGi support > > could be part of that and would also give folks ample time to reflect on > > Sounds good. > > > the feature, rather than rushing something new in without a good > > understanding of what it is / does and its implications. > > Well there really are several different aspects to the problem, > unfortunately some caused by the completely broken-by-design JAXP > mechanism ... It has its problems but it is the standard and would need a new revision of the specification to improve it if that's even possible at this point. Any change / enhancement would have to be backwards compatible with the current JAXP spec. Then there's all the other APIs (e.g. StAX, JAXB, JAX-WS, etc...) which have adopted similar patterns. If the Java platform had a modularization story earlier in the game (and not just thinking about introducing it now in Java 7) there might have been more hope for a better design. > ... and bad programming practices by applications. These need to be > addressed separately, probably in xml-commons (I've looked at the > FactoryFinder). But one problem at a time.. > > The patch I have so far addresses exactly one use case. I'll file a JIRA > tomorrow. > > thanks > Holger > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected]
