[Geoserver-devel] Weblogic Admin console broken due to setProperty

GeoServer GeoServer Developer
1

Hi Yohann, nice to meet you.

I'm cc'ing the geoserver devel list as someone else may have better clues.

Unfortunately I hadn't yet a chance to try to remove that dependency with
safety, as I'm not sure about the collateral damage it may cause.
On the bright side, we at TOPP are willing to build some sort of "server farm"
where we can more or less automate the functional testing of the product over
different servlet containers, which may be a good time to make the move.

So, when you say you're having the same issue with your product, is it using
geoserver and is geoserver who's causing you grief? or is it just your
product having the same issues but nothing to do with geoserver?

If the former, could you try building geoserver without that setting and
report back success/failure?
If the later, is it a possibility at all for you trying to get rid of it? is
there any reason you depend specifically of that transformer factory
implementation?

Yet, I don't think you're going to get too much a response if throwing this as
a weblogic bug report, as hardcoding the system property is just bad practice
imho, but anyhow let us know of any progress, its certainly something we
should solve asap.

Cheers,

Gabriel

On Thursday 27 December 2007 12:46:46 am you wrote:

Hi Gabriel,

Sorry to disturb you, you don't know me, but I saw your comment on codehaus
concerning the setProperty of the TransformerFactory that breaks the
weblogic admin console.
http://jira.codehaus.org/browse/GEOS-1094?page=com.atlassian.jira.plugin.sy
stem.issuetabpanels:all-tabpanel

We're having the exact same issue in our product :
System.setProperty("javax.xml.transform.TransformerFactory",
"org.apache.xalan.processor.TransformerFactoryImpl"); breaks the weblogic
admin console.

Did you find a solution to this problem ?

Looking at the Xalan documentation, there's not many way to set the
TransformerFactory :
http://xml.apache.org/xalan-j/usagepatterns.html#transformerfactory

Here are the three choices :
# Set the system property from the command line when you launch Java or
from within your application. # Set the system property in jaxp.properties
in the JAVA_HOME/lib directory, where JAVA_HOME is the root of the JDK. #
Revise the entry in src/META-INF/services and rebuild xalan.jar or
xercesImpl.jar, depending on which entry you have changed.

I think I will log a bug with WebLogic, or tell my customers that they
should put the missing jar files in weblogic's lib folder, but I would be
curious to know how you solved this on your end.

Thanks for your time and have good Holidays,

Yohann

!DSPAM:4045,4772e7f0300581431913854!

2

Hi again Gabriel,

My product is not related to geoserver.

In fact we removed the System.setProperty to get weblogic to work, but now the transforms are not proper on Oracle Application Server 10 (so far websphere, tomcat, jboss and weblogic are not giving any regressions).

I guess Oracle's transformer is not the regular one, and that's probably to avoid this kind of problem that the code was implemented this way.

So in the end we added an option to let the user call the setProperty or not.

Thanks for your answer anyway,

Cheers,

Yohann

-----Original Message-----
From: Gabriel Roldán [mailto:groldan@anonymised.com]
Sent: Wednesday, December 26, 2007 4:08 PM
To: Yohann Richard
Cc: 'Geoserver-devel'
Subject: Re: Weblogic Admin console broken due to setProperty

Hi Yohann, nice to meet you.

I'm cc'ing the geoserver devel list as someone else may have better clues.

Unfortunately I hadn't yet a chance to try to remove that dependency with safety, as I'm not sure about the collateral damage it may cause.
On the bright side, we at TOPP are willing to build some sort of "server farm"
where we can more or less automate the functional testing of the product over different servlet containers, which may be a good time to make the move.

So, when you say you're having the same issue with your product, is it using geoserver and is geoserver who's causing you grief? or is it just your product having the same issues but nothing to do with geoserver?

If the former, could you try building geoserver without that setting and report back success/failure?
If the later, is it a possibility at all for you trying to get rid of it? is there any reason you depend specifically of that transformer factory implementation?

Yet, I don't think you're going to get too much a response if throwing this as a weblogic bug report, as hardcoding the system property is just bad practice imho, but anyhow let us know of any progress, its certainly something we should solve asap.

Cheers,

Gabriel

On Thursday 27 December 2007 12:46:46 am you wrote:

Hi Gabriel,

Sorry to disturb you, you don't know me, but I saw your comment on
codehaus concerning the setProperty of the TransformerFactory that
breaks the weblogic admin console.

http://jira.codehaus.org/browse/GEOS-1094?page=com.atlassian.jira.plugi
n.sy
stem.issuetabpanels:all-tabpanel

We're having the exact same issue in our product :
System.setProperty("javax.xml.transform.TransformerFactory",
"org.apache.xalan.processor.TransformerFactoryImpl"); breaks the
weblogic admin console.

Did you find a solution to this problem ?

Looking at the Xalan documentation, there's not many way to set the
TransformerFactory :
http://xml.apache.org/xalan-j/usagepatterns.html#transformerfactory

Here are the three choices :
# Set the system property from the command line when you launch Java
or from within your application. # Set the system property in
jaxp.properties in the JAVA_HOME/lib directory, where JAVA_HOME is the
root of the JDK. # Revise the entry in src/META-INF/services and
rebuild xalan.jar or xercesImpl.jar, depending on which entry you have changed.

I think I will log a bug with WebLogic, or tell my customers that they
should put the missing jar files in weblogic's lib folder, but I would
be curious to know how you solved this on your end.

Thanks for your time and have good Holidays,

Yohann

!DSPAM:4045,4772e7f0300581431913854!