Caucho Forums  

This forum is permanently closed because of spam. For free community support, please visit Google Groups:


Go Back   Caucho Forums > Resin

Reply
 
Thread Tools Display Modes
  #1  
Old 03-26-2012, 04:21 PM
jalberto jalberto is offline
Junior Member
 
Join Date: Mar 2012
Location: London, UK
Posts: 24
Default Resin cannot access "http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd"

Hi,

Is there a way to tell Resin not to try going to "http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd" while deploying? Oracle has manage to break this URLs and now is almost impossible to deploy to resin4 without the server complaining of not being able to find the URL.

I am on Resin 4.0.24.

This looks like a critical matter, to avoid failure of external dependencies on live systems.

Jose Alberto
Reply With Quote
  #2  
Old 03-26-2012, 07:46 PM
alex alex is offline
Administrator
 
Join Date: Aug 2009
Posts: 218
Default

jalberto,

Can you set your logging level to finer or finest and post a stacktrace.

Thanks,
Alex
Reply With Quote
  #3  
Old 03-27-2012, 12:26 PM
jalberto jalberto is offline
Junior Member
 
Join Date: Mar 2012
Location: London, UK
Posts: 24
Default

Hummm,

It is working at the moment.

But the question is, does deployment validation actually accesses these external URLs and if so can it be changed to using a catalog so they are resolved against a cached copy.

These messing around by Oracle makes me realise how dependant we can get to external obscured points of failure.

If we see the error again, will post the stack trace on this thread.

Jose Alberto
Reply With Quote
  #4  
Old 03-28-2012, 02:29 PM
jalberto jalberto is offline
Junior Member
 
Join Date: Mar 2012
Location: London, UK
Posts: 24
Default

Ok found how to reproduce the problem.

If Our web.xml is defined by:


<web-app id="WebApp_ID" version="2.5" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd">
[...]
</web-app>

Resin will not deploy the application at all, due to the problem at java,sun.com.

But if I change it to:


<web-app xmlns="http://caucho.com/ns/resin" xmlns:resin="http://caucho.com/ns/resin/core">
[...]
</web-app>

It works, but of course it makes the web-app resin specific.

Hope you guys can come up with a solution.
Reply With Quote
  #5  
Old 03-28-2012, 05:17 PM
alex alex is offline
Administrator
 
Join Date: Aug 2009
Posts: 218
Default

Hm. I tested with that trying to reproduce it and did not see an exception or a message that would indicate resin trying to load the xsd.

It would help if you could copy the exact exception with stack trace, or an exact message. Resin shouldn't try loading that xsd as far as I know, so that's why an exact message/exception would help.

Thanks,
Alx
Reply With Quote
  #6  
Old 03-29-2012, 11:00 AM
jalberto jalberto is offline
Junior Member
 
Join Date: Mar 2012
Location: London, UK
Posts: 24
Default

Hi Alex,

We could not see an exception either, but the application simply will not deploy.

We are using versioning, we had a previous version running and in use. We deploy the app with the problematic web.xml and no new users could get in, the URLs of the app reporting 404. We changed the web.xml to use your resin specifics and the application deploys without any problem.

We are seen this behaviour in several other applications not running on resin. In particular if for some reason you are parsing XML with verification ON, it seems that some of the xml parsers get stuck when trying to use or access the schema definitions.

It could be that this is due to the java.sun.com URLs being redirected to some oracle HTML page instead of actually failling. We saw this behaviour on an application parsing with JDOM, for example. But I bet it is possibly a fault not of JDOM itself but on the xml parser implementations behind it. We all know this is a very narrow field.

We need you guys to raise the issue with Sun (a.k.a Oracle) about their removing these URLs which are mandatory on the JSR specs for JavaEE. As you are JavaEE certified they will have to listen to you. The more noise it can be made the better.

Even friends inside Oracle are seeing this problem and no one is paying attention to them. The blogosphere should be rampant about condemning Oracle about this.

Please help us all... We had waisted many man hours on a critical release schedule due to this arbitrary change by Oracle.

Jose Alberto
Reply With Quote
Reply

Tags
deployment issue, resin 4.0

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 11:37 PM.


Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.