Red Hat Bugzilla – Bug 163372
Perl action messages need to be used in java.
Last modified: 2007-04-18 13:29:23 EDT
Description of problem:
Action messages (The messages in the navy bluish bar near the top of a page)
that are created on a perl web page cannot be read on a java page.
Go to systems, click a system, delete the system. You are brought to the system
overview page without a message telling you that you have just deleted a system.
Now go to a pxt page. The message appears.
Messages will appear on the correct page regardless of whether that page is perl
These messages are saved in a session object on both sides. Neither side can
understand the other's session object. Since we are going to Java pretty soon,
we are not going to engineer a way to unstand perl session objects. Instead, we
will deal with each instance separately and pass the required information
through the request to the java page without pushing a message to the session.
So far the known times that a message need to go across the perl/java line are:
Creating a Server Group.
Deleting a Server Group.
Deleting a Server.
Deleting Servers (SSM).
qa contact == shughes
See Reproduce and Expected Results above.
The message should appear only once, on the page immediately after the action.
Browsing to one perl and one java page is enough to verify that the message only
This bug applies to any time an action is taken on the website that would
produce a message on the immediately following page AND the start and end page
are not written in the same language (perl to java or java to perl). So far,
the only known times this bug occurs there is a perl to java page order. These
known times are given in the previous comment.
looks good on qa