On 18/03/2011 13:02, Christophe Marchand wrote:
> Hi Mike,
> may I use external java function in XSLT with saon9 HE ?
> <xsl:value-of select="xem:generateUniqueID()" />
> This was perfectly working with saxon 188.8.131.52, but do not since I
> upgrate to Saxon184.108.40.206
As others have pointed out, this capability was not carried forward from
Saxon-B (9.1) to Saxon-HE (9.2).
This was a decision I took after very careful thought, and I knew it
would hurt some users - so I apologize to you if you are one of them.
The objective of the repackaging was to reduce the number of people who
were getting real commercial value from using Saxon and contributing
nothing back. I don't think it's a healthy situation when this occurs,
because it leads to under-investment in the product. I could point to
Orbeon as an example of what happens - it's a great piece of technology,
but it would be vastly better if its developers weren't having to earn a
living doing consultancy and only improving the product in their spare time.
This repackaging took place about 18 months ago, and I am pleased to say
that it achieved its objectives. I was concerned at the time that
development on the product was slowing down, because my time was
increasingly preoccupied with servicing the growing user base, and there
was not enough revenue coming in to increase the size of the team. Since
that decision was made (and I do think it is "propter hoc" as well as
"post hoc") license revenues have been growing very healthily, and I
have been able to take on a full-time developer as well as offloading
some of the administrative and commercial work.
I made the decision to remove extensions and extensibility features
partly because they accounted for more than their fair share of support
hassles, and I felt I could do a better job by wiping the slate clean
and thinking again; and partly because I wanted to give the open-source
user base a non-lethal electric shock, a wake-up call to remind them
that what you don't pay for, you shouldn't depend on. When you use an
open source product you can depend on it continuing to exist in
unchanged form, but you cannot assume that there will be a stream of new
releases or that they will be backwards-compatible. I was giving users
three options: stick with Saxon-B for ever, take the pain of converting
your applications to Saxon-HE, or open your wallet. It was the right
thing to do, and although I hate causing users trouble, it has ensured
the ability to continue developing the product to meet the
ever-increasing demands on it.
The hardest-hit users have been those who incorporate Saxon into other
open-source products, where using the commercial product is not an
option. I value these users because they often provide the most valuable
feedback, which benefits everyone. The reason I provided the new
extension function capabilities in Saxon-HE was specifically to ensure
that those users had a way forward, even though it might not be a