denuno/railo — comment on commit 2550b2c7b4dabba86cd8f2a89bf109a065718d4d
File:  line 0
By denuno:

Don't be! Your solution is much better. XML freaking sucks w/Java!!!

That reminds me-- the latest build of 3.3 is dieing because of a class
that is internal to sun, so the compiler won't import it.

I could modify the build scripts to use the ECJ compiler (from eclipse,
really nice actually) to get around it, as I know it works with internal
sun classes, but maybe you have a better idea.

The nice thing about ECJ is that then we don't even need a JDK to
compile Railo.

The class that won't compile with a sun compiler is:
railo.runtime.text.pdf.PDFDocument
because of the import of
com.sun.xml.internal.messaging.saaj.util.ByteInputStream

:Denny

On 11/11/11 1:45 PM, Michael Offner wrote:
> sorry for rejecting, i have made bad experience by extending a dom object
> on string level.
> serialization is based on the jre and not every jre use the same engine.
>
> /micha
>
>
> 2011/11/11 denstar <
> reply@reply.github.com
>>
>
>> AWESOME, you da man, Micha! Looks beautiful. Much better!
>>
>> On 11/11/11 5:51 AM, Michael Offner wrote:
>>> see also ticket https://issues.jboss.org/browse/RAILO-1618
>>>
>>> ---
>>> Reply to this email directly or view it on GitHub:
>>>
>> https://github.com/denuno/railo/commit/2550b2c7b4dabba86cd8f2a89bf109a065718d4d#commitcomment-710948
>>
>> ---
>> Reply to this email directly or view it on GitHub:
>>
>> https://github.com/denuno/railo/commit/2550b2c7b4dabba86cd8f2a89bf109a065718d4d#commitcomment-711774
>>
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/denuno/railo/commit/2550b2c7b4dabba86cd8f2a89bf109a065718d4d#commitcomment-712027