Incompatible Xalan

[Mike Bailey]

NB 6.1: I seem to be experiencing an old problem that has never been adequately resolved: I need xalan.jar in my RCP application because some of my code has been explicitly written to it. But when it's there, a zipped distribution of my application won't launch on a Mac because:

"An incompatible Xalan version has been detected on the IDE's classpath. The IDE cannot start. Please see http://wiki.netbeans.org/wiki/view/FaqXalanOnCP for more information."

That page, and others which are somewhat related, does not adequately describe the root of the problem nor a sensible way to address it. Apparently:
1. Apache's xalan has some bug in it (according to NB folks) which screws up the project system in the platform.
2. Instead of working around it, it was decided to simply throw up the above message then terminate.
3. In the 1-2 years since this was discovered, no fix has been forthcoming from the Apache team.

Point #3 is hard to believe, but c'est la vie.

The reference wiki page must have been written before there was such a thing as a Netbeans Platform application, because the work around (using two versions of the JRE) is a non-starter for customers as opposed to developers.

In searching this list and other places, there seems to be a property value (netbeans.do.not.check.xalan) which might assist in this confusion, but where and how to set it among the several modules that make up my application is unclear, and several attempts have proven unsuccessful.

I'd appreciate hearing from anyone who has successfully mastered this roadblock.

Mike Bailey
[e-mail]

[Emilian Bold-2]

I don't know anything about this error, but just to make it clear:
xalan is a library wrapper you use ? Or something you add the the boot
classpath of the platform ?

Also, most likely the netbeans.do.not.check.xalan must be set in the
etc/netbeans.conf with -J-Dnetbeans.do.not.check.xalan=true . There's
also an property you can use for the site but I forgot it; the problem
is that afaik, it doesn't propagage to the conf file.

PS: After reading the FAQ in the wiki it's quite clear that you have
an altered JRE. Could you try using a library wrapper instead and
leave the JRE clean ?

--emi



On Sat, Sep 13, 2008 at 12:22 AM, Mike Bailey <jmbailey@...> wrote:

> NB 6.1: I seem to be experiencing an old problem that has never been
> adequately resolved: I need xalan.jar in my RCP application because some of
> my code has been explicitly written to it. But when it's there, a zipped
> distribution of my application won't launch on a Mac because:
>
> "An incompatible Xalan version has been detected on the IDE's classpath. The
> IDE cannot start. Please see http://wiki.netbeans.org/wiki/view/FaqXalanOnCP
> for more information."
>
> That page, and others which are somewhat related, does not adequately
> describe the root of the problem nor a sensible way to address it.
> Apparently:
> 1. Apache's xalan has some bug in it (according to NB folks) which screws up
> the project system in the platform.
> 2. Instead of working around it, it was decided to simply throw up the above
> message then terminate.
> 3. In the 1-2 years since this was discovered, no fix has been forthcoming
> from the Apache team.
>
> Point #3 is hard to believe, but c'est la vie.
>
> The reference wiki page must have been written before there was such a thing
> as a Netbeans Platform application, because the work around (using two
> versions of the JRE) is a non-starter for customers as opposed to
> developers.
>
> In searching this list and other places, there seems to be a property value
> (netbeans.do.not.check.xalan) which might assist in this confusion, but
> where and how to set it among the several modules that make up my
> application is unclear, and several attempts have proven unsuccessful.
>
> I'd appreciate hearing from anyone who has successfully mastered this
> roadblock.
>
> Mike Bailey
> jmbailey@...
> ________________________________
> View this message in context: Incompatible Xalan
> Sent from the Netbeans - Open API mailing list archive at Nabble.com.
>

--
Emilian Bold
[phone]
http://www.emilianbold.ro

Java and NetBeans Platform-loving consulting services from Timisoara, Romania.

[Fabrizio Giudici]

I think it's on the classpath, right? I've experienced an even more crazy problem that triggered even putting it into a wrapper module:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6396599

Basically, it breaks java.util's Preferences on Linux!! What I discovered to work, according a suggestion of that bug report, is to remove the META-INF/services directory from xalan.jar and put into a wrapper module. In this way it is not installed by default, while the code that needs it (Batik in my case) seems to work properly - I suppose that it asks explicitly for it when it sets up the factories etc.

Emilian Bold wrote

I don't know anything about this error, but just to make it clear:
xalan is a library wrapper you use ? Or something you add the the boot
classpath of the platform ?

Also, most likely the netbeans.do.not.check.xalan must be set in the
etc/netbeans.conf with -J-Dnetbeans.do.not.check.xalan=true . There's
also an property you can use for the site but I forgot it; the problem
is that afaik, it doesn't propagage to the conf file.

PS: After reading the FAQ in the wiki it's quite clear that you have
an altered JRE. Could you try using a library wrapper instead and
leave the JRE clean ?

--emi



On Sat, Sep 13, 2008 at 12:22 AM, Mike Bailey jmbailey@... wrote:
  

NB 6.1: I seem to be experiencing an old problem that has never been
adequately resolved: I need xalan.jar in my RCP application because some of
my code has been explicitly written to it. But when it's there, a zipped
distribution of my application won't launch on a Mac because:

"An incompatible Xalan version has been detected on the IDE's classpath. The
IDE cannot start. Please see http://wiki.netbeans.org/wiki/view/FaqXalanOnCP
for more information."

That page, and others which are somewhat related, does not adequately
describe the root of the problem nor a sensible way to address it.
Apparently:
1. Apache's xalan has some bug in it (according to NB folks) which screws up
the project system in the platform.
2. Instead of working around it, it was decided to simply throw up the above
message then terminate.
3. In the 1-2 years since this was discovered, no fix has been forthcoming
from the Apache team.

Point #3 is hard to believe, but c'est la vie.

The reference wiki page must have been written before there was such a thing
as a Netbeans Platform application, because the work around (using two
versions of the JRE) is a non-starter for customers as opposed to
developers.

In searching this list and other places, there seems to be a property value
(netbeans.do.not.check.xalan) which might assist in this confusion, but
where and how to set it among the several modules that make up my
application is unclear, and several attempts have proven unsuccessful.

I'd appreciate hearing from anyone who has successfully mastered this
roadblock.

Mike Bailey
jmbailey@...
________________________________
View this message in context: Incompatible Xalan
Sent from the Netbeans - Open API mailing list archive at Nabble.com.

    

[Mike Bailey]

And grazie molte to you sir!  A very logical suggestion, of course, removing the library from the service-provider discovery system, yet leaving it for the use of code in my module.
Life is beautiful once again.
Mike Bailey
[e-mail]

Fabrizio Giudici wrote:

...
remove the META-INF/services directory from xalan.jar and put into a
wrapper module. In this way it is not installed by default, while the
code that needs it
...