Error Page flow in sp2

I was using weblogic platform sp1 and upgraded to sp2 .
In sp2 i get following error during build.
ERROR: Controller.jpf:287: There is no @jpf:forward with the
return-action attribute defined for this nested PageFlowController.
ERROR: SUGGESTION: Create a @jpf:forward annotation on an action
method and mark it with a return-action attribute.
Can any one help in solving this problem
tia
Mahesh

Thanks for your reply
I tried by reinstalling SP2
its same error
Mahesh
"R Kucera" <[email protected]> wrote:
>
Mahesh,
SP2 upgrade doesn't work. Download the entire SP2 and do a net install
from scratch.
-R
"Mahesh" <[email protected]> wrote:
I was using weblogic platform sp1 and upgraded to sp2 .
In sp2 i get following error during build.
ERROR: Controller.jpf:287: There is no @jpf:forward with the
return-action attribute defined for this nested PageFlowController.
ERROR: SUGGESTION: Create a @jpf:forward annotation on an action
method and mark it with a return-action attribute.
Can any one help in solving this problem
tia
Mahesh

Similar Messages

Error page flow weblogic sp2

I was using weblogic platform sp1 and upgraded to sp2 .
In sp2 i get following error during build.
ERROR: Controller.jpf:287: There is no @jpf:forward with the
return-action attribute defined for this nested PageFlowController.
ERROR: SUGGESTION: Create a @jpf:forward annotation on an action
method and mark it with a return-action attribute.
Can any one help in solving this problem
tia
Mahesh

Mahesh,
David is correct about the requirement for the return-action attribute but I
believe this was just as true in the initial 8.1 release.
- john
"David Karr" <[email protected]> wrote in message
news:40631e05$[email protected]..
>
I can give you a little background on the problem, which may lead you to asolution.
>
When you have a nested page flow, there has to be some way to get out ofthe nested
page flow and back to the containing page flow. You can see this in theFlow
View with an action that connects with the red box. The connection betweenthat
action and the red box represents a jpf:forward with a return-actionattribute.
The value of the "return-action" attribute is the name of the action tocall
in the calling page flow.
You can see useful examples of this in the Avitek EvalGuide example, inthe "RegisterReferralController.jpf"
for example.
As you say you're just upgrading from sp1 to sp2, I would guess that therewas
a change in whether a forward with "return-action" was required or not. Ihave
no idea.
"Mahesh" <[email protected]> wrote:
I was using weblogic platform sp1 and upgraded to sp2 .
In sp2 i get following error during build.
ERROR: Controller.jpf:287: There is no @jpf:forward with the
return-action attribute defined for this nested PageFlowController.
ERROR: SUGGESTION: Create a @jpf:forward annotation on an action
method and mark it with a return-action attribute.
Can any one help in solving this problem
tia
Mahesh

EmptyStackException when exit from nested page flow on SP2

I have tried to call a nested page flow (TestNestedController.jpf) from page flow
and using redirect="true". After exit from nested page flow, it supposes that
return to the action testNestedDone() in page flow(TestPageController). It works
on SP1, but it fails on SP2.
Please suggest any solutions for this issues.
public class TestPageController extends PageFlowController
// Uncomment this declaration to access Global.app.
// protected global.Global globalApp;
// For an example of page flow exception handling see the example "catch"
and "exception-handler"
// annotations in {project}/WEB-INF/src/global/Global.app
* This method represents the point of entry into the pageflow
* @jpf:action
* @jpf:forward name="success" path="page.jsp"
protected Forward begin()
return new Forward("success");
* @jpf:action
* @jpf:forward name="success" path="/test/testNested/TestNestedController.jpf"
redirect="true"
protected Forward goToNested()
System.out.println("go to nested redirect = true");
return new Forward("success");
* @jpf:action
* @jpf:forward name="success" path="index.jsp"
protected Forward testNestedDone()
return new Forward("success");

The error message like this:
Empty nesting stack for returned action BackToPrevious from Page Flow /xxxx/viewMemberController.jpf.
com.bea.wlw.netui.pageflow.EmptyNestingStackException: Empty nesting stack for
returned action BackToPrevious from page flow /xxxx/viewMember/viewMemberController.jpf.
at com.bea.wlw.netui.pageflow.FlowController.forwardTo(FlowController.java:1103)
"patrick" <[email protected]> wrote:
>
I have tried to call a nested page flow (TestNestedController.jpf) from
page flow
and using redirect="true". After exit from nested page flow, it supposes
that
return to the action testNestedDone() in page flow(TestPageController).
It works
on SP1, but it fails on SP2.
Please suggest any solutions for this issues.
public class TestPageController extends PageFlowController
// Uncomment this declaration to access Global.app.
// protected global.Global globalApp;
// For an example of page flow exception handling see the example
"catch"
and "exception-handler"
// annotations in {project}/WEB-INF/src/global/Global.app
* This method represents the point of entry into the pageflow
* @jpf:action
* @jpf:forward name="success" path="page.jsp"
protected Forward begin()
return new Forward("success");
* @jpf:action
* @jpf:forward name="success" path="/test/testNested/TestNestedController.jpf"
redirect="true"
protected Forward goToNested()
System.out.println("go to nested redirect = true");
return new Forward("success");
* @jpf:action
* @jpf:forward name="success" path="index.jsp"
protected Forward testNestedDone()
return new Forward("success");

Page flow exception

I have one serious problem when handling exception in page flow. ie.
my code looks like,
// Generated by WebLogic Workshop
// Created on: Mon Dec 01 15:31:45 GMT+05:30 2003
// By: kshashishekar
package portlets.validation.validation;
import com.bea.wlw.netui.pageflow.FormData;
import com.bea.wlw.netui.pageflow.Forward;
import com.bea.wlw.netui.pageflow.PageFlowController;
import com.bea.wlw.netui.tags.html.TreeNode;
import javax.security.auth.login.FailedLoginException;
import javax.servlet.http.HttpServletRequest;
import org.apache.struts.action.ActionErrors;
import org.apache.struts.action.ActionMapping;
import org.apache.struts.action.*;
import com.login.CustomLogin;
import com.bea.p13n.controls.login.UserLoginControl;
* @jpf:controller struts-merge="struts-config-portlets-validation-validation2.xml"
* @jpf:message-resources resources="validation.validator.Message"
* @jpf:view-properties view-properties::
* 
* <view-properties>
* <pageflow-object id="pageflow:/portlets/validation/validation/validationController.jpf"/>
* <pageflow-object id="action:begin.do">
* <property value="280" name="x"/>
* <property value="60" name="y"/>
* </pageflow-object>
* <pageflow-object id="action:validate1.do#portlets.validation.validation.validationController.ValidateForm">
* <property value="220" name="x"/>
* <property value="200" name="y"/>
* </pageflow-object>
* <pageflow-object id="action:logout.do#portlets.validation.validation.validationController.ValidateForm">
* <property value="120" name="x"/>
* <property value="100" name="y"/>
* </pageflow-object>
* <pageflow-object id="action-call:@page:validate1Page1.jsp@#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="384,320,320,256" name="elbowsX"/>
* <property value="172,172,192,192" name="elbowsY"/>
* <property value="West_1" name="fromPort"/>
* <property value="East_1" name="toPort"/>
* </pageflow-object>
* <pageflow-object id="page:validate1Page1.jsp">
* <property value="420" name="x"/>
* <property value="180" name="y"/>
* </pageflow-object>
* <pageflow-object id="action-call:@page:Result.jsp@#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="156,170,170,184" name="elbowsX"/>
* <property value="332,332,203,203" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_2" name="toPort"/>
* </pageflow-object>
* <pageflow-object id="page:Result.jsp">
* <property value="120" name="x"/>
* <property value="340" name="y"/>
* </pageflow-object>
* <pageflow-object id="page:/error.jsp">
* <property value="40" name="x"/>
* <property value="180" name="y"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#validate1Page1.jsp#@action:begin.do@">
* <property value="316,350,350,384" name="elbowsX"/>
* <property value="52,52,172,172" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#Result.jsp#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="184,170,170,156" name="elbowsX"/>
* <property value="192,192,332,332" name="elbowsY"/>
* <property value="West_1" name="fromPort"/>
* <property value="East_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#validate1Page1.jsp#@action:logout.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="156,270,270,384" name="elbowsX"/>
* <property value="92,92,172,172" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="control:com.bea.p13n.controls.login.UserLoginControl#myControl">
* <property value="28" name="x"/>
* <property value="34" name="y"/>
* </pageflow-object>
* <pageflow-object id="formbeanprop:portlets.validation.validation.validationController.ValidateForm#username#java.lang.String"/>
* <pageflow-object id="formbeanprop:portlets.validation.validation.validationController.ValidateForm#password#java.lang.String"/>
* <pageflow-object id="formbean:portlets.validation.validation.validationController.ValidateForm"/>
* </view-properties>
public class validationController extends PageFlowController
* This is the control used to generate this pageflow
* @common:control
private UserLoginControl myControl;
// Uncomment this declaration to access Global.app.
// protected global.Global globalApp;
// For an example of page flow exception handling see the example "catch"
and "exception-handler"
// annotations in {project}/WEB-INF/src/global/Global.app
* This method represents the point of entry into the pageflow
* @jpf:action
* @jpf:forward name="success" path="validate1Page1.jsp"
protected Forward begin()
return new Forward( "success" );
* @jpf:action validation-error-page="validate1Page1.jsp"
* @jpf:forward name="success" path="Result.jsp"
* @jpf:catch method="exceptionHandler" type="Exception"
protected Forward validate1(ValidateForm aForm) throws Exception
com.bea.p13n.usermgmt.profile.ProfileWrapper var = myControl.login( aForm.username,
aForm.password, getRequest());
getRequest().setAttribute( "results", var );
return new Forward("success",aForm);
* Action encapsulating the control method :logout
* @jpf:action
* @jpf:forward name="success" path="validate1Page1.jsp"
* @jpf:catch message="not authenticated" path="/error.jsp" type="Exception"
public Forward logout( ValidateForm aForm )
throws Exception
myControl.logout( getRequest() );
return new Forward( "success" );
* @jpf:exception-handler
* @jpf:forward name="errorPage" path="/error.jsp"
protected Forward exceptionHandler( Exception ex, String actionName, String
message, FormData form )
String displayMessage = "An exception occurred in the action " + actionName;
System.out.println ("display message "+displayMessage);
getRequest().setAttribute( "errorMessage", displayMessage );
return new Forward( "errorPage" );
* FormData get and set methods may be overwritten by the Form Bean editor.
public static class ValidateForm extends org.apache.struts.validator.ValidatorForm
private String password;
private String username;
public void setUsername(String username)
this.username = username;
public String getUsername()
return this.username;
public void setPassword(String password)
this.password = password;
public String getPassword()
return this.password;
* added just to test validate (override) method.
public ActionErrors validate(ActionMapping map, HttpServletRequest req)
ActionErrors errors = null;
try {
errors = super.validate(map,req);
}catch (Exception e)
e.printStackTrace();
if (errors ==null) {
System.out.println ("errors = "+errors);
} else
System.out.println ("errors= "+errors);
return errors;
in the above code when we call "validate1" action, it will authenticate successfully
when we enter valid username and passowrd.
But when i enter invalid credentials page flow controller should execute "handleException"
method but at this time i am getting an error
Page Flow Unhandled Exception
Exception: java.lang.IllegalArgumentException
Message: argument type mismatch
A java.lang.IllegalArgumentException exception was thrown and not handled by any
Page Flow. See the console for the exception stack trace.
please help us on how to rectify this error.
thanks,
shashi
[validationController.jpf]

Hi-
That may be on the right track, but the /index.jsp page gets displayed in the
portlet...I am still within the portal framework, so I don't think I am loosing
the context...
-Howie
"Khurram Zafar" <[email protected]> wrote:
>
you are most likely redirecting to the /error.jsp page and losing the
context for
your portal app. The index.jsp page may be defined as your <welcome-file>
in your
web.xml file. The best thing to do is to save the context before visiting
error.jsp
and then provide a link in error.jsp to go back. Look at javadoc for
PageURL for
obtaining the URL to a portal page, you can then save it in session of
pass it
to your error page.
"Howie Oakes" <[email protected]> wrote:
Hello-
I have a page flow portlet that I am testing some exception handling
on. Right
now when I catch an exception, I display the global /error.jsp page,
using the
@jpf:catch tag. The problem is when I refresh the page after viewing
the error
page, the pageflow always pulls up the /index.jsp page at the root of
the webapp.
I have to get a new session to see the original page flow.
This only happens when I am running the Jpf as a portlet...I don't see
this behavior
with it stand-alone.
I am not sure why the index.jsp page is being called...there are noreferences
to it in my jpf code...
thanks,
Howie

How to change the "Page Flow Error - Unsatisfied Role Restriction" page

When you try to access a page and are denied authorization to it, Weblogic automatically redirects you to a
"Page Flow Error - Unsatisfied Role Restriction" page, on the bottom of which tells you what roles you have to be in in order to access the resource. My question is how can I change this page to match the general look and feel of my application?

I know you asked this almost a month ago, so you may have already figured it out... but you just need to add a handler for com.bea.wlw.netui.pageflow.UnfulfilledRolesException. Something like this:
@jpf:catch type="com.bea.wlw.netui.pageflow.UnfulfilledRolesException" path="roles-error.jsp"
You can put it at the class level of a specific page flow, or at the class level of WEB-INF/src/Global.app, which will apply it to all page flows.
Hope this helps.
Rich

JDev 10.1.3 Errors BME-01605 and BME-99033 in Struts Page Flow

Hi All,
I get the following error when I choose the Data Page icon in Struts Page Flow and try to drag into the diagram. Any ideas???
Thanks!!!
java.lang.NullPointerException     at oracle.bm.diagrammer.registry.RBaseShape.setDefaultCore(RBaseShape.java:539)
at oracle.bm.diagrammer.shape.BaseDiagramShape.initProperties(BaseDiagramShape.java:450)
at oracle.bm.diagrammer.shape.BaseDiagramShape.initShape(BaseDiagramShape.java:322)
at oracle.bm.diagrammer.shape.BaseDiagramNode.initShape(BaseDiagramNode.java:291)
at oracle.adfdt.controller.struts.diagram.shape.StrutsActionNode.initShape(StrutsActionNode.java:68)
at oracle.bm.diagrammer.BaseDiagram.addShape(BaseDiagram.java:6913)
at oracle.adfdt.controller.diagram.PageFlowDiagram.addShape(PageFlowDiagram.java:197)
at oracle.bm.diagrammer.BaseDiagram.addShape(BaseDiagram.java:6838)
at oracle.bm.diagrammer.track.CreateRegisteredShapeTracker.doCreateNode(CreateRegisteredShapeTracker.java:715)
at oracle.bm.diagrammer.track.CreateRegisteredShapeTracker$6.performAction(CreateRegisteredShapeTracker.java:297)
at oracle.bm.diagrammer.LockMonitor.performLockedAction(LockMonitor.java:64)
at oracle.bm.diagrammer.BaseDiagram.performDiagramLockedAction(BaseDiagram.java:2429)
at oracle.bm.diagrammer.track.CreateRegisteredShapeTracker.processEvent(CreateRegisteredShapeTracker.java:279)
at oracle.bm.diagrammer.track.TrackerStack.processEvent(TrackerStack.java:403)
at oracle.bm.diagrammer.track.TrackerStack.pop(TrackerStack.java:198)
at oracle.bm.diagrammer.track.RectangularTracker.mouseReleased(RectangularTracker.java:441)
at oracle.bm.diagrammer.track.ModularTracker.processEvent(ModularTracker.java:196)
at oracle.bm.diagrammer.track.TrackerStack.processEvent(TrackerStack.java:389)
at oracle.bm.diagrammer.BaseDiagramView$53.processEvent(BaseDiagramView.java:719)
at oracle.bm.diagrammer.PageView$PageViewPanel.fireEvent(PageView.java:2904)
at oracle.bm.diagrammer.PageView$PageViewPanel.processEvent(PageView.java:3097)
at java.awt.Component.dispatchEventImpl(Component.java:3955)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1774)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

Never mind!!! I restarted Jdeveloper and now works!!!
Sorry

[[ Page Flow Error - Action Not Found ]] - urgent help needed!

Hi all,
My portal application runs on Weblogic 8.1 and I am encountering a vague error which does not point back to any of the application-based files. The error message, as stated in the subject, is
"Page Flow Error - Action Not Found"
I did modify the url-template-config.xml under groWeb/WEB_INF to add a new template to enforce secure access to application resources. Could this have caused the above error?
Any feedback would be greatly appreciated!!
Thanks.

Here is just a portion of Page Controller class
package com.amd.portal.presentation.GeneralRegistration
public class GeneralRegistrationController extends PageFlowController
* @jpf:action
* @jpf:forward name="success" path="RegistrationConfirmation.jsp"
* @jpf:validation-error-forward name="failure" path="index.jsp"
public Forward registerUser(RegisterUserForm register_form)
usermanager_ctrl.registerUser(register_form, this.getRequest());
return new Forward( "success", register_form);
Here is a portion of the code from the JSP that uses this controller
<netui:form action="registerUser">
<tr valign="top">
<td><font color="red"> * </font> User Name:</td>
<td>
<netui:textBox dataSource="{actionForm.userName}"/>
Â Â Â
<netui:error value="userName"/>
</td>
</tr>
<tr valign="top">
<td><font color="red"> * </font> Password:</td>
<td>
<netui:textBox dataSource="{actionForm.password}" password="true" />
Â Â Â
<netui:error value="password"/>
</td>
</tr>
<netui:button value="Submit" type="submit"/>
</netui:form>
This apparently doesn't display well when posted but I can email to you if you provide me with your email address. Thanks.
- CW
Message was edited by:
lcwalters

Custom Error Pages in EP 6.0 SP2

Hello,
Can anyone tell me if there is a way to setup custom error pages in Ep 6.0 SP2.
Thanks,
Keith

Hi Praveen,
What are trying to see if there is a way to have custom error messages in the SAP Portal J2EE Engine.
For example if you have an IIS or Apache server you can setup custom 500 or 404 error pages, is this possible within the SAP J2EE Engine?
Thanks,
Keith

SAP BPC 5.1 SP2 Http 500 internal server error - page can not be displayed

When our Sysadmin service account are restricted to the app server and the database server ( as they should be in a secured environment) no client
could reach the web site to even use the Osoft directory . We get a Http 500 internal server error - page can not be displayed . This is for a new multiserver install. Is there a problem on the website security or .net configuration?

Yes the install was done by the SAP install consultant but now we are getting an error when we restrict the Sysadmin ID. Server diagnostics and other tests on Appshell passed as well.

Workshop CRASHED while editing a page flow

Workshop Gurus -
Any clues on this bug. I get this error while editing pageflow. It just started
happening this morning.
I must say, WLW crashes gracefully. It allows me to report this message directly
to BEA, and then allows me to save my files. However, I do need a resolution to
this problem, hopefully soon.
java.lang.NullPointerException
     at workshop.pageflow.model.ExternalPageFlow.refChanged(ExternalPageFlow.java:120)
     at workshop.pageflow.model.DocumentEventAdapter.processModelObjects(DocumentEventAdapter.java:492)
     at workshop.pageflow.model.DocumentEventAdapter.process(DocumentEventAdapter.java:177)
     at workshop.pageflow.model.DocumentEventAdapter.elementChange(DocumentEventAdapter.java:123)
     at com.bea.ide.element.ElementChangeSupport.fireListeners(ElementChangeSupport.java:253)
     at com.bea.ide.element.ElementChangeSupport.fireElementChange(ElementChangeSupport.java:243)
     at com.bea.ide.element.ElementChangeSupport.fireElementChange(ElementChangeSupport.java:219)
     at com.bea.ide.document.DefaultDocument.fireElementChildRemoved(DefaultDocument.java:482)
     at com.bea.ide.sourceeditor.DefaultSourceDocument.mergeComplete(DefaultSourceDocument.java:523)
     at com.bea.ide.sourceeditor.DefaultSourceDocument.mergeMetadata(DefaultSourceDocument.java:610)
     at workshop.sourceeditor.compiler.CompilerProject$MergeRunner.run(CompilerProject.java:1448)
     at workshop.sourceeditor.compiler.CompilerSvcImpl$TreeMergeLock.runMerger(CompilerSvcImpl.java:161)
     at workshop.sourceeditor.compiler.CompilerProject$4.run(CompilerProject.java:1498)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:448)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
Thanks
Kunal Mittal

Raj -
Yes I am using SP2. I have had Workshop crash SEVERAL times when working with
page flows. Some sort of null pointer exception. The only good thing is that workshop
crashes gracefully, so I didn't lose any work that I was doing.
Thanks.
Kunal
"Raj Alagumalai" <[email protected]> wrote:
Kunal,
Can you try using SP2 ?
Thanks,
Raj Alagumalai
Backline Workshop Support
"Kunal Mittal" <[email protected]> wrote in message
news:[email protected]...
Workshop Gurus -
Any clues on this bug. I get this error while editing pageflow. Itjust
started
happening this morning.
I must say, WLW crashes gracefully. It allows me to report this messagedirectly
to BEA, and then allows me to save my files. However, I do need aresolution to
this problem, hopefully soon.
java.lang.NullPointerException
atworkshop.pageflow.model.ExternalPageFlow.refChanged(ExternalPageFlow.java:12
0)
atworkshop.pageflow.model.DocumentEventAdapter.processModelObjects(DocumentEve
ntAdapter.java:492)
atworkshop.pageflow.model.DocumentEventAdapter.process(DocumentEventAdapter.ja
va:177)
atworkshop.pageflow.model.DocumentEventAdapter.elementChange(DocumentEventAdap
ter.java:123)
atcom.bea.ide.element.ElementChangeSupport.fireListeners(ElementChangeSupport.
java:253)
atcom.bea.ide.element.ElementChangeSupport.fireElementChange(ElementChangeSupp
ort.java:243)
atcom.bea.ide.element.ElementChangeSupport.fireElementChange(ElementChangeSupp
ort.java:219)
atcom.bea.ide.document.DefaultDocument.fireElementChildRemoved(DefaultDocument
.java:482)
atcom.bea.ide.sourceeditor.DefaultSourceDocument.mergeComplete(DefaultSourceDo
cument.java:523)
atcom.bea.ide.sourceeditor.DefaultSourceDocument.mergeMetadata(DefaultSourceDo
cument.java:610)
atworkshop.sourceeditor.compiler.CompilerProject$MergeRunner.run(CompilerProje
ct.java:1448)
atworkshop.sourceeditor.compiler.CompilerSvcImpl$TreeMergeLock.runMerger(Compi
lerSvcImpl.java:161)
atworkshop.sourceeditor.compiler.CompilerProject$4.run(CompilerProject.java:14
98)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:448)
atjava.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.ja
va:197)
atjava.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
Thanks
Kunal Mittal

Message resources from page flow

How can I access the ResourceBoundle declared at the top of the page flow, from
the page flow?

I have a question that goes along with this...
Can you add formatting with any of these different bundle options? Since
8.1 SP2 now has the attribute "accessKey" on buttons, we'd like to be able
to underline the letter we are using for the accessKey. Our attempt at
using the message bundle just puts the formatting inside the button value.
When the jsp displayed this was the value shown for the button text: <u> S
</u>ubmit
Is this possible to do without using javascript? One of our team members
found a script that adds the underline, but there is alot of code to
underline one letter.
Ideas?
Thank you!
Wendy
"John Rohrlich" <[email protected]> wrote in message
news:[email protected]...
Gus,
Your welcome.
You don't need to get the bundle and pass it. You can access it directly
from the JSP. If these are validation error messages you can use the
<netui:error> tag. If the string you want to access is not for displaying
validation errors you'll want to access the strings in another manner. The
documentation in
http://edocs.bea.com/workshop/docs81/doc/en/workshop/guide/netui/guide/conDatabindingXScript.html
shows at least 3 approaches. Here is the relevant section from that
document.
bundle
The bundle data binding context references properties that you define in a
message resources file, which allows you to implement internationalizedweb
applications by not hard-coding text labels in your JSP pages.
For example, in your page flow controller class, you can add an annotation
such as the following:
* @jpf:controller
* @jpf:message-resources resources="labels.Messages"
public class Controller extends PageFlowController
{ ...In this example, the naming convention is that the message resources
file must be located in the project's /WEB-INF/classes/labels directory,and
the file must be named Messages.properties.
In the Messages.properties file, you might have a property such as:
nameLabel=Name Then in your JSP page, you can use a data bindingexpression
such as the following:
<netui:label value="{bundle.default.nameLabel}"/> Alternately, you can use
the key attribute on the @jpf:message-resources annotation:
In your page flow controller class annotation:
* @jpf:controller
* @jpf:message-resources key="foo" resources="labels.Messages"
public class Controller extends PageFlowController
{ ...Assume that the Messages.properties file in the
/WEB-INF/classes/labels directory is the same as shown in the previous
example. In the JSP page, you could use a tag such as the following:
<netui:label value="{bundle['foo/jpfDirectory'].nameLabel}"/> In this
case, your page flow controller class file is/jpfDirectory/Controller.jpf.
>
Another option is to use the <netui-data:declareBundle> tag. For example,in
your JSP page:
<netui-data:declareBundle name="someMessages"
bundlePath="com/foobar/resources/WebAppMessages"/>This tag declares abundle
that can be referenced in a data binding expression, such as in the
following example:
<netui:label value="{bundle.someMessages}"/> For more information, see the
topics about the @jpf:message-resources Annotation and the
<netui-data:declareBundle> Tag.
"Gus" <[email protected]> wrote in message
news:[email protected]...
First of all, thanks!
I want to get a string from the bundle and pass it to a JSP in therequest.
I have defined the resources at the top of the JPF, as specified in thehelp:
@jpf:message-resources resources="mensajes"
The question is how can I get a string from the mensajes.properties
file.
>>
Gus
I would be better able to answer your question if I knew what you
wanted
to
do. Are you trying to display the strings from the bundle?
john
"Gus" <[email protected]> wrote in message
news:[email protected]...
How can I access the ResourceBoundle declared at the top of the pageflow,
from
the page flow?

error-page in web.xml not working

In my web.xml I have
<error-page>
<exception-type>java.lang.NullPointerException</exception-type>
<location>/error.jsp</location>
</error-page>
I checked the page works by doing a /context/error.jsp and
the page displays fine (it is a simple jsp page).
I hit a struts action that gives me this in the std output.
06/29 10:48:24 error
[1]java.lang.NullPointerException
at
com.pearson.gs.cms.business.LoginService.verifyPassword(LoginService.java:232)
at
com.pearson.gs.cms.action.LoginAction.performCMSAction(LoginAction.java:92)
at
com.pearson.gs.cms.action.BaseCMSAction.execute(BaseCMSAction.java:48)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at
jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at
jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:259)
at
jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541)
at
jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
[0]javax.servlet.ServletException
at
org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:523)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at
jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at
jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:259)
at
jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541)
at
jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
I get a 500 error page instead of my /error.jsp page.
I tried adding
<error-page>
<error-code>500</error-code>
<location>/error.jsp</location>
</error-page>
but that doesn't work either.
JRun 4.0
Updater 6
JDK 1.4.2
Struts 1.2.8
Any ideas what to try?

a. Override your skeletons error.jsp to forward/redirect to your page.
or
b. If you primarily use pageflow portlets Define a shared flow which has an exception handling method and direct it to your page. Reference the shared flow in each of your controllers (i think global.app is deprecated in 10 otherwise you could do this there). this lets you log some additional information, plus gives you the added flexibility of dealing with different exception types
or
c. Override the path to error.jsp in your portlets properties (havent tested)
Note if you are using servlets etc you still need your web.xml java.lang.Exception entry. The reason it doesnt get picked up is because the portal framework is handling the exception
Edited by: deepshet on Dec 22, 2008 8:12 PM

JSF tags are not rendered in error page

I have configured error page for HTTP 404 error in web.xml like this
<error-page>
<error-code>404</error-code>
<location>/Common/error.jspx</location>
</error-page>
Faces Servlet is configured as follows
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
My error page (error.jspx) looks like this
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1" xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html" xmlns:trh="http://myfaces.apache.org/trinidad/html"
xmlns:tr="http://myfaces.apache.org/trinidad" xmlns:c="http://java.sun.com/jsp/jstl/core">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<html>
<head>
<title>Error Page</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body id="b1">
<h4 style="color:red">An Error Occured. Please click Back button or Signout.</h4>
<input type="button" value="Back" onclick="history.back()"/>
<tr:commandButton id="cb1" text="SIGN OUT" action="exit" actionListener="#{Login.LogOut}"/>
</body>
</html>
</jsp:root>
When I deploy application and run into 404 error, page displays error message with only Back button. I don't see SingOut button. I have checked url and it follows /faces/* pattern. Still to double check, I made a change and configured servlet mapping in web.xml as
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
<url-pattern>*.jspx</url-pattern>
</servlet-mapping>
Still commandButton is not rendered. I understand that my error page don't have access to FacesContext or not going through Faces Servlet. I know this is a small issue, but couldn't figure out what can be done. I have also tried using .xhtml and .jsf as per googled suggestion. But no luck
I have tried different solutions to my problem and googled for solutions. But I couldn't get it resolved.
So can you please provide any suggestions...
Edited by: user1818355 on May 22, 2013 2:29 PM

I think my faces servlet is configured to handle URLs having /faces/* pattern. I don't have any folder named with faces but I can access all my web pages which have /faces/ in their url. All jspx pages in application are configured in task flows. So I think they have access in FacesContext. But error page is configured in only web.xml and some how it is missing access to FacesContext and not rendering JSF tags. Any help?

Global error page for portal project

Hi
This is regarding weblogic 8.1.
We have a portal project which contains several portlets. For handling exceptions
in a page flow we have a global error page at the project root level and each
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed in the portlet
context. How can we make this error page to take up the whole screen and display
it outside of the portlet context so that all other links within the portal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer

Sameer,
Please post this question to the weblogic.developer.interest.portal
newsgroup.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Sameer Dalal" <[email protected]> wrote in message
news:3f4bd37f$[email protected]..
>
Hi
This is regarding weblogic 8.1.
We have a portal project which contains several portlets. For handlingexceptions
in a page flow we have a global error page at the project root level andeach
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed inthe portlet
context. How can we make this error page to take up the whole screen anddisplay
it outside of the portlet context so that all other links within theportal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer

Global Error page in portal

Hi
This is regarding weblogic portal 8.1.
We have a portal project which contains several portlets. For handling exceptions
in a page flow we have a global error page at the project root level and each
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed in the portlet
context. How can we make this error page to take up the whole screen and display
it outside of the portlet context so that all other links within the portal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer

Also, you could do this:
* @jpf:catch type="Exception" method="handleAllExceptions"
* @jpf:exception-handler
* @jpf:forward name="errorPage" path="/error.jsp" redirect="true"
protected Forward handleAllExceptions( Exception e, String actionName,
String message, FormData form )
return new Forward( "errorPage" );
In this case, handleAllExceptions() will redirect to the error page, which
will bring you out of the portal.
Rich
"Subbu Allamaraju" <subbuATbeaDOTcom> wrote in message
news:3f4cdefa$[email protected]..
Sameer,
The portal rendering framework renders the error page inside portlet
windows to address the most common scenario, where failure in a given
portlet won't stop users from interacting with other portlets.
Here are the options you've to address your use case:
- Handle the exception in the pageflow itself, and do a sendRedirect()
to the error page. This would bypass rendering of other portlets, and
user will be redirected to the error page.
- If the source of the exception is the JSP, you'll have to add some
javascript in the error page to do a redirect or, better yet, replace
the markup.
Subbu
Sameer Dalal wrote:
Hi
This is regarding weblogic portal 8.1.
We have a portal project which contains several portlets. For handling
exceptions
in a page flow we have a global error page at the project root level andeach
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed inthe portlet
context. How can we make this error page to take up the whole screen anddisplay
it outside of the portlet context so that all other links within theportal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer

Error Page flow in sp2

Similar Messages

Maybe you are looking for