Alternative to org.apache.pluto.useJaxp system property for 1.1.5

Eric Dalquist <[email protected]> Mon, 04 Feb 2008 12:31:25 -0600
Newsgroups gmane.comp.jakarta.pluto.user
Organization DoIT
Message-ID <[email protected]>
I would like to propose an alternative to the org.apache.pluto.useJaxp 
system property. The problem with the property for our use case is we 
know the user will be running in a JDK1.5+ environment and we would like 
a way to ensure JAXP is used by Pluto without having to make sure the 
user has configured the start scripts for their container correctly.

I have a few ideas for possible solutions:

1. Simple JDK version checking. Use 
System.getProperty("java.specification.version") to determine the JDK 
version and choose the appropriate Castor configuration to use. That 
property returns values such as: 1.1, 1.2, 1.3, ...

2. Look for a pluto_descriptor.properties file in the classpath. Before 
checking the system property check if a file 
/pluto_descriptor.properties exists in the classpath and read the 
property from that file. That would allow Pluto implementers to include 
a .properties file with the correct configuration for their portal.

3. Make a portal callback API to determine the configuration. This would 
be fairly complex as I'm thinking the descriptor service would need to 
queue up parsing of the descriptor XML files until the portal context 
was up and running and could provide the configuration.


I'm more than happy to implement any of the solutions or consider others.

Thanks
-Eric
||

||
smime.p7s (application/x-pkcs7-signature, 3.3 KB) - not displayed