Viewing applet via webserver causes hanging, locally it will run fine

RESOLVED EXPIRED

Status

Core Graveyard
Java: OJI
--
critical
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Wolfgang Grinfeld, Assigned: Nidheesh Dubey)

Tracking

({hang})

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

16 years ago
Trying to use Xalan XSLT on Mozilla 1.1 Alpha within an applet causes the 
browser to hang if running in a webserver (Tomcat 4.0).
Opening the same page without a webserver will run the Applet OK.
This is using jdk 1.4.0_01.
(Reporter)

Comment 1

16 years ago
Created attachment 90959 [details]
test page

Test page to allow XSLT to work as an applet in Netscape/Mozilla
(Reporter)

Comment 2

16 years ago
Created attachment 90963 [details]
applet using xalan XSLT processor

Updated

16 years ago
Keywords: hang
(Reporter)

Comment 3

16 years ago
Xalan software can be found at http://xml.apache.org/xalan-j/
The version used is 2.4.D1
(Reporter)

Comment 4

16 years ago
Using java 1.4.1 beta improves usage of applets in that some of them run,
however Xalan software still gives trouble

Comment 5

16 years ago
Reporter, can you try it with Netscape 4.7x, and see what happens? How about IE?

Comment 6

16 years ago
Re-assign to Nidheesh.
Assignee: joe.chou → nidheesh

Updated

16 years ago
QA Contact: pmac → petersen

Comment 7

14 years ago
Isn't this a Java 1.4.x bug or a Xalan bug rather than a Mozilla bug?
Does this work with a recent Mozilla and java VM?
How does this goes on Netscape 4.x or IE?

Comment 8

14 years ago
Any update regarding this bug?
Was it tried with Netscape 4.7* and IE (see Comment #5, dated 2002)?
You mention Xalan 2.4.1, How about Xalan 2.6? Does the newer release help?
You mention that Java 1.4.1 beta improves things. How About new Java 1.5?
Did you try on another platform then Windows NT
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED

Updated

8 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.