Exiting a page flow

Hi guys, and thanks a lot for answering my previous questions.
Now i am wondering; is there a way to explicitly exit a page flow?
Regards,
Håvard Nesvold

Sathish-
Through the use of custom and standard controls, I have incorporated authentication
and user management in my jsps. There is a netui tag that you can utilize to
reference a control. I have found the easiest way to add a control is to drag
it from my tree onto the JSP.
As for getting pageFlow into my header, I haven't tried yet.
Eric
"Sathish Venkatesan" <[email protected]> wrote:
>
Eric,
I have checked with support. This functionality is not supported in the
current
release.
I want to try a different approach.
I want to use a custom java control in jsp ?
Did you had a chance to try it out and had any luck ?
thanks,
sathish
"Eric Ballou" <[email protected]> wrote:
Sathish-
Have you tried a global pageflow? Also, did you include the netui tags
in the
pageflow? I personally have thought about doing the same, but I was
concerned
about using the jsp:include as some session information doesn't always
transfer
or call properly in an include. One idea may be to use a reference/render
to
a portlet. Those are just approach ideas I haven't tried, but may soon.
Hope
that at least gives you a starting point.
Eric
"Sathish Venkatesan" <[email protected]> wrote:
Hi all,
I want to include a page flow in header section of a portal.
I tried with JSP:include tag , but I'm getting message unable to find
action .
Is it possible ?
thanks,
sathish

Similar Messages

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");

Struts Page Flow Diagram

I am using JDeveloper 10.1.2. When I drag and drop a component onto the Struts Page Flow diagram, nothing is placed on the diagram. I've checked the thumbnail and there are no components on it. I followed some instructions I found in a previous post (Re: Struts Page Flow Diagram ( In Reply To : Struts Page Flow Diagram ) Oct 13, 2004 11:48 AM
Reply
Weird -
First of all just check the shape has not been created "off-screen" by using the Thumbnail view.
If not can you do a refresh diagram from the context menu? (Diagram -> Refresh diagram from Struts config).
If that does not work then exit Jdev, navigate to the ViewController project on disk and delete the /model/StrutsPageFlow.oxd_struts file.
The when you next open the struts-config.xml the diagram will be re-generated.
I've pasted in your config and a diagram was generated ok.) and still the drag and drop is not placing the component on the page flow diagram. One thing that I have noticed -- there is NO CODE in the source file for the struts-config.xml file. Any ideas on what I am doing wrong? Thanks!

More info: I can place a page component on my page flow diagram but I cannot place any other components. They won't display. Placing the page component on the diagram does not put code into the source file. Also, I get the following compile error: Error(1,1):<Line 1, Column 1>:XML-20108:(Fatal Error) Start of root element expected.
Thanks!

Nested page flow navigation problem

I created a portlet based on a page flow, pf1. pf1 invokes an action "callPageFlow2"
to call a nested page flow 'pf2'. When I navigate from pf1 to pf2, everything
is OK. But if I click the BROWSER's "Back" button to move back from pf2 to pf1,
then click the link to invoke "callPageFlow2" again, I got the error saying "callPageFlow2
not found". In fact the portal was looking for "callPageFlow2" within pf2 instead
of pf1 (although I click the link within pf1).
If I run the page flow I did not get this error. Only when I tried this within
a portal, it failed.
Any idea?
Thanks

The browser back button has been a perpetual pain in the neck for server side applications,
but the truth is, if it's causing any problems, then the application design should
be revisited. In this particular case, when you call pf2, portal server marks
pf2 as the current pageflow in session so that future actions can be invoked on
this pageflow. pf1 is pushed onto a stack also tracked in the session. When you
exit from pf2 through an exit action, the stack is popped and pf1 is set as the
current pageflow BUT when you go back by pressing the back button, the server
never gets a chance to pop the stack and reset pf1 as the current pageflow. Hence
when you submit an action belonging to pf1, the server chokes because it can't
find the action on pf2 which has been pinned as the current pageflow because of
the previous request that did hit the server.
SO, a possible fix is that the underlying pageflowcontroller code is modified
to lookup the action in the parent pageflow if the action is not found in the
nested pageflow. I hope BEA will make that fix. You do have a workaround which
should work in most of the cases. If the action is not found in the current pageflow,
portal server DOES look for the action in another place, and that is the Global
pageflow as defined in the Global.app file. So as a workaround, if your flow logic
will allow it, you can duplicate the actions called on pf1 in the global.app.
You DO NOT need to duplicate all the actions, just the one or two that are on
the JSP that allows you to invoke callPageFlow2. Make sure you edit your jsp paths
in the forwards to point to absolute paths from the root of your app instead of
relative paths that you may have.
I tried to hack around this using the backing file mechanism, but the server chokes
before it gets to any of the backing class methods, so I resorted to this work
around temporarily.
Cheers
Khurram
"zli" <[email protected]> wrote:
>
I created a portlet based on a page flow, pf1. pf1 invokes an action
"callPageFlow2"
to call a nested page flow 'pf2'. When I navigate from pf1 to pf2, everything
is OK. But if I click the BROWSER's "Back" button to move back from pf2
to pf1,
then click the link to invoke "callPageFlow2" again, I got the error
saying "callPageFlow2
not found". In fact the portal was looking for "callPageFlow2" within
pf2 instead
of pf1 (although I click the link within pf1).
If I run the page flow I did not get this error. Only when I tried this
within
a portal, it failed.
Any idea?
Thanks

Page flow stopped

I have been editing a chapter for three days with no problems, and out of the blue, the page flow stopped, and I can't get the paragraphs to advance to the next page. I have tried the following things:
checking to make sure the current and next pages have the same flow. (They do.)
saving and closing the file, exiting FrameMaker, and restarting my computer
using a different paragraph tag
turning off track text edits and attempting to advance to the next page with unmarked text
entering preview mode with track text edits turned off
I have the following set up:
FrameMaker 9.0p237
Windows 7 64bit
A very robust computer
A client with an insane deadline
Please help!
Thanks,
Karen

Karen, as you're on a deadline I'd suggest that it's easier to resurrect the file by creating a new file rather than troubleshooting what went wrong with the current file.
1. save your current file as-is, so that you're sure you have both the content that you've entered and the formatting. Personally I'd also do a second backup copy of the problem file with a different name, e.g. xxBAD or something.
2. create a brand new FM file. With both documents open, in the new file do File > Import > Formats, and select the "old" file in the drop-down menu. Then select which will copy all the master pages and paratags etc. over to your new file. Save this new file with a different name, "xxNew". Be sure to note what settings you've selected on the bottom section "While updating remove", so that if you need to you can re-do the import and change these settings. The initial selection depends on how many style overrides you might have used (if any) in the original document.
3. In the xxNew file, put your cursor in the text frame at the top of the first (and so far only) page. Then do File > Import > File. Choose the xxOld file. At the bottom of the dialog be sure to select "copy into document". This will copy the content from the other file into the xxNew file.
In the "Import text flow" dialog that pops up, choose the Body page flow and the default "A (Main Flow)". Because you've already imported the formats you could use either the default "Reformat Using current document's formats" or the bottom "Retain Source's Formatting" -- the choice depends a lot on whether you have ad hoc formatting in your original document, e.g. highlighted words and just clicked "Bold" from the menu, as opposed to using a character style called "Bold", or changed the alignment of a paragraph but not made a new paragraph tag for that different alignment, both of those examples are of overrides. If you have used a lot of overrides then I would suggest using "Retain source's formatting".
4. In the xxNew file, page to the end of the document. Put your cursor before the "end of flow" symbol,
Start typing, enter a few carriage returns, whatever, to be sure that when you reach the end of the page that FM will automatically add a new page and your typing does extend forward onto the next page as you expect.
Assuming things are ok, then save this xxNew file as the original filename.
That should get you back to operation, and you can work out what went wrong with the original file once the deadline has passed.
Sheila

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

Multiple Browsers with the same Page Flow

I have a legacy application that I am working on migrating to Weblogic. The
legacy application allowed the user to have multiple windows of the same
module open at the same time. Users found this useful if they wanted to look
at two different records in the same module. For example, if you had a
registration app and you wanted to look at Joe's registration information
and Sue's registration. Is it possible to have two browsers within the same
session open and pointing to the same RegistrationController.jpf?
Thank You.
Michelle

I believe our problem is that our form beans are class members of the page
flow thus when you open another instance of the same controller the form
beans are overwritten. Our GUI is displayed as modules containing multiple
tabs with a form bean for each tab. The module has a controller, signifying
the page flow for the module. So, one record in a module will span multiple
tabs. We did not want to have one big form bean that is why we multiple
form beans. But it now looks like we will need to store these form beans
perhaps to the session in a collection identified by the window instance
they belong to.
We also need to do multiple different page flows but I don't think nested
page flows will not work here because the page flows would almost need to be
nested of each other. I guess you could almost think of as each module is
an independent application however some can be invoked by others.
<Rich Feit> wrote in message news:[email protected]..
Hi Michelle,
Yes, that should be just fine. That page flow will remain the "current
page flow" as requests from both browser windows hit it. The NetUI
runtime synchronizes the action methods, so you don't need to worry about
thread-safety within them.
There's also a way to have multiple different active page flows at the
same time, but in this case you don't need to do anything special.
Rich

Multiple instances of Page Flows

I have a legacy application that I am working on migrating to Weblogic. The
legacy application allowed the user to have multiple windows of the same
module open at the same time. Users found this useful if they wanted to look
at two different records in the same module. For example, if you had a
registration app and you wanted to look at Joe's registration information
and Sue's registration. Is it possible to have two browsers within the same
session open and pointing to the same RegistrationController.jpf?
We currently have our form beans stored in the page flow which seems to
cause a problem as when we open another browser instance in the same session
pointing to the same page flow, the form beans from the first window are
overwritten. An approach we are possbily looking at is to store the form
beans in an object in the session and identify a set of form beans as
belonging to a particular window instance - perhaps by uniquely naming the
windows as they are opened.
Has anyone done this before with needing to have multiple instances of the
same page flow or multiple instances of different non-nested page flows open
at the same time?
Michelle

Hi Vijay,
Thanks for the reply, But that's not the right aproach.
I cannot change the application to stateless, Since the standard application where the page resides is statefull.
Also some of the business logic I cannot achive with stateless application
Regards
Geogy

Communication between multiple page flow portlets

Hi, I am working on weblogic portal 8.1.
I've been struggling to communicate between different page flow portlets,
I have a login page flow portlet and i need to submit login details to indeex page after login action is done.
I am able to do this by using PageUrl class and RequestDispatcher's forward method using definition label of the index page flow portlet.
but it is not happening again when i logged out.
If anybody have worked on it, please let me know the soltution.
Thanks,
Vidya sagar

Not sure whether you tried this option(I tried it works for me).
configuration has to be done is portlet-2:
=========================
Create an custom event namely(messageCustomEvent) and also add an action for it for invoking a portlet method getMessage in Portlet-2.
//Place this method in Portlet-2
public void getMessage(ActionRequest request, ActionResponse response,
Event event) {
CustomEvent customEvent = (CustomEvent) event;
String message = (String) customEvent.getPayload();
response.setRenderParameter("message0", message);
configuration has to be done is portlet-1:
=========================
when click on Login in portlet1, in the pageflow code you fire an custom event as shown below
PortletBackingContext context =
PortletBackingContext.getPortletBackingContext(getRequest());
context.fireCustomEvent("messageCustomEvent", form.getMessage());
return new Forward("success");
Thanks & Regards,
Murali.
============

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

How to submit a form with checkboxes in a page flow?

I'm having some trouble with a form that contains several checkboxes, and
how to submit this form within a page flow...
I have a JSP page containing a form with N checkboxes. The value and
checked/unchecked status of each checkbox is generated from parsing an XML
document. Here is the (simplified) code:
<%@ taglib uri="http://java.sun.com/jstl/xml" prefix="x" %>
<netui:form action="doUpdate">
<x:forEach select="...">
<input type="checkbox" name="id"
<x:if ...>checked</x:if> value="<x:out ... />">
</x:forEach>
<netui:anchor formSubmit="true" action="doUpdate">Submit</netui:anchor>
<netui:anchor action="doCancel">Cancel</netui:anchor>
</netui:form>
When this form is submitted, the checkbox values are lost -- the following
code (in the action) produces an empty array:
String[] prefs = this.getRequest().getParameterValues("id");
I looked at the <netui:checkbox> tag, but it does not appear to give me a
way to set the state and value (unless I've missed something).
Can I submit a form without using a form bean? If I do use a form bean, can
I set the state and value from my JSP?
Any suggestions on how to do this (or insights into what I'm doing wrong)
are welcome...
-- Craig

I am new to this, but I think this may solve your problem:
I am not sure if this is what you are looking for, but you can create a LinkedHashMap
with the req key/value pairs in the page-calling action in the pageflow and then
pass that via a getRequest().setAttribute("myCheckboxes",myCheckboxHashMap);
You can then access it in code using the optionsDataSource portion of the netui:checkBoxGroup
- ie
<netui:checkBoxGroup dataSource="{actionForm.thisCheckbox}" optionsDataSource="{request.myCheckboxes}">
Hope this helps!
m
"Craig Coffin" <craig+1268fbec@nfld-dot-com> wrote:
I'm having some trouble with a form that contains several checkboxes,
and
how to submit this form within a page flow...
I have a JSP page containing a form with N checkboxes. The value and
checked/unchecked status of each checkbox is generated from parsing an
XML
document. Here is the (simplified) code:
<%@ taglib uri="http://java.sun.com/jstl/xml" prefix="x" %>
<netui:form action="doUpdate">
<x:forEach select="...">
<input type="checkbox" name="id"
<x:if ...>checked</x:if> value="<x:out ... />">
</x:forEach>
<netui:anchor formSubmit="true" action="doUpdate">Submit</netui:anchor>
<netui:anchor action="doCancel">Cancel</netui:anchor>
</netui:form>
When this form is submitted, the checkbox values are lost -- the following
code (in the action) produces an empty array:
String[] prefs = this.getRequest().getParameterValues("id");
I looked at the <netui:checkbox> tag, but it does not appear to give
me a
way to set the state and value (unless I've missed something).
Can I submit a form without using a form bean? If I do use a form bean,
can
I set the state and value from my JSP?
Any suggestions on how to do this (or insights into what I'm doing wrong)
are welcome...
-- Craig

Drag and drop STILL sketchy in Struts Page Flow

Struts Page Flow has been a major problem area in JDev since it was introduced, and I am still having some useability issues with it.
I CANNOT drag an application module method out, onto a data action; if the data action isn't one of the newest actions on the page. If the action has more than one target, (multiple "forwards") or just isn't one of the "newest" actions on the page, the GUI shows me dragging a the method from an app mod out onto the action, but no work is done once I drop it. I must delete the data action, and re-create it. This, in the mean time, will overwrite any data action class I had defined originally.
This needs to be fixed very soon, as it has been in every build of 10g that I have dealt with.

Ok. To reproduce the bad drag and drop behavior:
Create a Misc Data page, name it "Home"
Drag a data page out, name it "A", and put stuff on it. (Doesn't need to be complex).
Drag an action out, name it "B".
Drag another action out, name it "C"
Connect a forward from "A" to "B", connect a forward from "B" to "C". Connect a forward from "C" to "Home".
Connect a "fail" forward back, from "B" to "A".
Try to drag a method off of an applicaiton module to Action "B". It should not work.

How do I redirect request to an external page flow?

Hi,
I´m really stucked here. I need to redirect and XML wich I get in page flow to an external page flow(in a different project(war) but in the same workshop application(ear)), I´ve tryied all kinds off things but it does not work correctly.
I even tryied what is written in workshop docs:
If the path begins with a protocol such as "http:" the page flow runtime will look outside of this web application for the resource, and it will automatically cause a redirect (rather than a server forward) to the resource. If the path begins with a forward slash, "/", the runtime will start at the web application's root directory to locate the resource. If the path omits the forward slash, "/", the reference is relative to the page flow's directory.
so I did:
@jpf:forward name="goToKnapp" path="http://localhost:7001/eaiKnapp/PageFlowName.jpf"
and inside the method:
return new Forward("goToKnapp");
and it does´t work.
Any help will be wellcome.

Go to iPhoto and hit File and go to EXPORT. From there you can export your entire iPhoto Library to your external drive in any folder you want. Now if you've named the pictures in iPhoto and you select the check box for NAME and Keywords in the EXPORT menu the photos will be exported with the names given in iPhoto and any keywords you have added to the photo such as a description.. Hope this helps not sure if this is what your looking for.

Code to call another Page Flow URL from one page flow URL

Can anyone send me the code to call another pageflow url from one page flow URL.

thanks...
In my appication there is no Form page. Only based on Canvas in that ,
i implemented Text box, Text Field And Drop down list etc..by own coding without using any abstract methods.
I did every thing with in single Midlet file.While developng goes on i got the problem ,
Like "your application exceeds the memorylimit you cant
use more than 32Kb of byte code in Canvas"...
So the application is not opened.
I tried to call the next file in same package to proceed, i got it. codition goes to next file, but its not return back to the Main(MIDlet) file, throws the excepton as "Security exception".
How to solve this problem,is any other way? please...

Using a control implimentaion file in BEA page flows?

I'm using BEA Weblogic 9.2 and I've created a custom JDBC control to use in my project with page flows.
My control has 4 files:
1.) myModel.java: contains the class that represents the table.
2.) myControl.java: the interface for the control.
3.) myControlDB.java: public interface that extends jdbcControl and contains the basic operations for the database. No actual methods, just sql commands in the annotations.
4.) myControlImpl.java: Contains the business logic for the control and has the @ControlImplimentation annotation.
However, I'm not sure what purpose the "control implimentation" file servers. I can't use it in the page flows, and I can't add it to the "referenced controls" list.
How do I use this control implementation in my page flows?

Hi,
Does your custom control appear in the insert -> control -> existing control option ?
Can you also verify that the corresponding method is created in the custom control interface
In the source view, place the cursor on the custom control method, and enter Ctrl + 1, select the create in super type option. This should create the corresponding method in the interface.
I've also listed the link to our documentation which explains in detail about using database controls
http://e-docs.bea.com/workshop/docs92/ws_platform/controls/system/jdbc/navDatabaseControl.html
-Raj

Exiting a page flow

Similar Messages

Maybe you are looking for