[xmlc] Re: Re: Issues with XMLC 2.3.2

This is a multi-part message in MIME format...

------------=_1299527188-30467-14639
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Well, it is not really a patch, but something that made my use case one 
working...I agree nowdays it would be reasonable to move XMLC to JDK1.5 
or even 1.6...

Thanks a lot for the quick response!

Sasa.


On 07-Mar-11 17:13, Jacob Kjome wrote:
> I can look into using your patch for #1 (or something like it) for the 
> next XML release.  I think the primary issue here is that we've 
> maintained a dependency on JDK1.3, which does not have java.net.URI.  
> I've tried to maintain this minimum dependency as long as Xerces does 
> so.  Plus it makes for easy testing because JDK1.3 doesn't add any of 
> its own XML libraries.  It's easy to dictate the version without 
> getting buggy JDK1.4 XML behavior.  But I think most of the world has 
> moved on to JDK1.5+, so maybe XMLC should too at some point?
>
> I'll have to test #2.  Not sure how quickly I'll be able to get to 
> this, though.  But I'll try and spend some time this week on it.
>
> Jake
>
> On Mon, 07 Mar 2011 13:56:15 +0100
>  Sasa Bojanic <[email protected]> wrote:
>> Hi,
>>
>> I'm trying to upgrade our applications that use XMLC 2.3.1 to the 
>> newest XMLC version.
>> Our applications are deployed both under the Tomcat 6.0.29 
>> application server and Enhydra application server (based on Tomcat 
>> 6.0.29).
>>
>> There are two issues I faced:
>>
>> 1) when deploying under the Tomcat, XMLC JAR files are placed 
>> together with the application JAR files into application's 
>> WEB-INF\lib folder (so application classloader is used to load them). 
>> In this case, XMLC can't load resources (*.html and *.xmlc files) 
>> from JAR file. When resources are not in the JAR file but unpacked 
>> into WEB-INF\classes folder everything works.
>>
>> After "patching" the method getPathURLFromClasspath() from 
>> XMLCDeferredParsingFactory to add:
>>
>>        if (srcURL != null && srcURL.toString().indexOf(".jar") >= 0) {
>>              try {
>>                 String mdurl = srcURL.toString();
>>                 srcURL = new URL("jar:"
>>                                  + mdurl.substring(0, 
>> mdurl.indexOf(".jar")) + ".jar!/"
>>                                  + 
>> mdurl.substring(mdurl.indexOf(".jar") + 4));
>>              } catch (Exception ex) {
>>           }
>>        }
>>
>> after the line:
>>
>>        URL srcURL = fDynamicClassLoader.getResource(path);
>>
>> it works fine.
>>
>> 2) when deploying under Enhydra application server or under Tomcat, 
>> but instead of putting XMLC JAR files into application's WEB-INF\lib, 
>> we put it into Tomcat's lib folder, XMLC can't find resources no 
>> matter if resources are inside JAR file or unpacked, and it can't 
>> find it even in the case I put application's JAR file into Tomcat's 
>> lib folder.
>>
>> Is it a bug in XMLC? Can somebody help?
>>
>> Regards,
>> Sasa.
>>
>


------------=_1299527188-30467-14639
Content-Type: text/plain; charset="UTF-8"; name="message-footer.txt"
Content-Disposition: inline; filename="message-footer.txt"
Content-Transfer-Encoding: quoted-printable


--
You receive this message as a subscriber of the [email protected] mailing list=
.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=3Dhelp
OW2 mailing lists service home page: http://www.ow2.org/wws

------------=_1299527188-30467-14639--