This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 133282 - generated war file does not externally deploy
Summary: generated war file does not externally deploy
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 5.x
Hardware: Other Linux
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-20 02:05 UTC by wbmarvin
Modified: 2008-08-27 10:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
error messages when opening jsp page on unbundled tomcat (45.58 KB, text/plain)
2008-04-20 02:09 UTC, wbmarvin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description wbmarvin 2008-04-20 02:05:02 UTC
Project builds and runs fine using embedded tomcat server. When deployed to tomcat 5 it goes haywire when jsp pages are
referenced. The deployed war file appears to have been exploded properly
Comment 1 wbmarvin 2008-04-20 02:09:25 UTC
Created attachment 60453 [details]
error messages when opening jsp page on unbundled tomcat
Comment 2 Petr Hejl 2008-04-21 09:44:17 UTC
Please specify the exact steps to reproduce and the exact version of the tomcat you are deploying to. Looks like
misconfigured tomcat instance: "The type java.lang.Object cannot be resolved. It is indirectly referenced from required
.class files".
Comment 3 wbmarvin 2008-04-21 16:22:26 UTC
1) load fedora 9
2) enable tomcat5 from services menu on gnome
3) move war file to /usr/share/tomcat5/webapps/pagecouunter.war
4) observe directory /usr/share/tomcat5/webapps/pagecouunter is created
5) observe java -version prints 1.5.0_09
Comment 4 Petr Hejl 2008-06-25 11:45:15 UTC
Is this issue still valid in Fedora 9 FCS? According to reported log this seems to be problem with Fedora 9 environment
(java.lan.Object missing during the compilation).
Comment 5 Petr Hejl 2008-07-17 09:56:34 UTC
No response from reporter. Closing as WORKSFORME.
Comment 6 wbmarvin 2008-07-17 14:12:13 UTC
This turns out to be a tomcat design flaw.  Tomcat superimposes a new security manager on the scene, one that does not
follow the standard java applet sandbox model. further, since the applet actually runs on a foreign machine, It can only
be changed at the remote machine... you might as well use a signed applet :( The tomcat people take the position that
their software don't have to actually work, being a work of art and all LOL. The work around is to embed files to be
used by unsigned applets as properties this works fine. As far as I can tell it is impossible to reference an external
file from an unsigned applet using tomcat, even one that resides on the originating server
Comment 7 Petr Hejl 2008-08-13 09:59:26 UTC
Honestly I do not understand the last comment. How it is related to original issue?

The original comment seems to be caused by somehow misconfigured tomcat. Is it reproducible in fedora 9 stable?
Comment 8 Petr Hejl 2008-08-27 10:49:43 UTC
No response from reporter. Closing as WORKSFORME.