Troubleshooting page flow apps (evalguide, in particular)

What facilities are there for troubleshooting pageflow problems? I'm looking at
the Avitek evalguide application, and I'm finding that a link goes to a completely
different page than the manual (and the code, seemingly) indicates. Are there
any useful diagnostics I can turn on at the pageflow level, and perhaps at the
webapp api level? I imagine there should be some diagnostics available at the
Struts level, so I'll have to remind myself how to increase the output of that
(unless someone remembers).
I've already eliminated what I think are the obvious issues, like checking the
security-constraints settings in the web.xml or any filters. I can't find anything
that helps me there.

"Mindy" <[email protected]> wrote in message
          news:402a4528$[email protected]..
          >
          > Is there a way to get the NT login name of a user in the page flows and
          jsp? We
          > want to authenticate a user belongs to a group before giving him access to
          a site
          > so the first thing in the begin method in page flow will be to get his
          login name
          > and then we have another module which validates the user belongs to a
          particular
          > group.
          Two possibilities spring to mind, NTRealm which is a security realm for
          weblogic that works with NTLM, I have no personal experience with it however
          you can search edocs for more info about it. Another alternative is jCIFS
          which includes an NTLM authentication handler for HTTP. I have used this in
          a previous life and it works great. You can view more info about it here
          http://jcifs.samba.org/src/docs/httpclient.html.
          Gerald
          

Similar Messages

  • 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

  • Transaction rolled back in Page Flow

    I am getting the following exceptions out of nowhere. It's non-deterministic, it just happens from time to time. The same steps can lead to normal behaviour or this error... It all ends with timed out exception. I don't know what is causing it, I don't know how to fix it. Does anyone have any ideas?
    From the log:
    |javax.ejb.TransactionRolledbackLocalException
    javax.ejb.TransactionRolledbackLocalException: Client's transaction aborted
         at com.sun.ejb.containers.BaseContainer.useClientTx(BaseContainer.java:2267)
         at com.sun.ejb.containers.BaseContainer.preInvokeTx(BaseContainer.java:2147)
         at com.sun.ejb.containers.MessageBeanContainer.beforeMessageDelivery(MessageBeanContainer.java:906)
         at com.sun.ejb.containers.MessageBeanListenerImpl.beforeMessageDelivery(MessageBeanListenerImpl.java:38)
         at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:131)
         at $Proxy62.invoke(Unknown Source)
         at com.stc.bpms.bpelConnector.impl.AbstractWSProvider.invoke(AbstractWSProvider.java:105)
         at com.stc.bpms.bpelImpl.runtime.Interpreter$1.run(Interpreter.java:661)
         at com.stc.bpms.bpelConnector.impl.ExecutorImpl$WorkImpl.run(ExecutorImpl.java:338)
         at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:54)
         at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)
    |#]
    [#|2008-01-29T13:15:24.015+0100|INFO|IS5.1.3|javax.enterprise.system.container.ejb.mdb|_ThreadID=39; ThreadName=Worker: 24;stacktrace-id=1;|javax.ejb.TransactionRolledbackLocalException
    javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested exception is: javax.ejb.TransactionRolledbackLocalException: Client's transaction aborted
    javax.ejb.TransactionRolledbackLocalException: Client's transaction aborted
         at com.sun.ejb.containers.BaseContainer.useClientTx(BaseContainer.java:2267)
         at com.sun.ejb.containers.BaseContainer.preInvokeTx(BaseContainer.java:2147)
         at com.sun.ejb.containers.MessageBeanContainer.beforeMessageDelivery(MessageBeanContainer.java:906)
         at com.sun.ejb.containers.MessageBeanListenerImpl.beforeMessageDelivery(MessageBeanListenerImpl.java:38)
         at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:131)
         at $Proxy62.invoke(Unknown Source)
         at com.stc.bpms.bpelConnector.impl.AbstractWSProvider.invoke(AbstractWSProvider.java:105)
         at com.stc.bpms.bpelImpl.runtime.Interpreter$1.run(Interpreter.java:661)
         at com.stc.bpms.bpelConnector.impl.ExecutorImpl$WorkImpl.run(ExecutorImpl.java:338)
         at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:54)
         at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)
    javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested exception is: javax.ejb.TransactionRolledbackLocalException: Client's transaction aborted
         at com.sun.ejb.containers.BaseContainer.checkExceptionClientTx(BaseContainer.java:2570)
         at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2422)
         at com.sun.ejb.containers.MessageBeanContainer.afterMessageDelivery(MessageBeanContainer.java:1056)
         at com.sun.ejb.containers.MessageBeanListenerImpl.afterMessageDelivery(MessageBeanListenerImpl.java:46)
         at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:154)
         at $Proxy62.invoke(Unknown Source)
         at com.stc.bpms.bpelConnector.impl.AbstractWSProvider.invoke(AbstractWSProvider.java:105)
         at com.stc.bpms.bpelImpl.runtime.Interpreter$1.run(Interpreter.java:661)
         at com.stc.bpms.bpelConnector.impl.ExecutorImpl$WorkImpl.run(ExecutorImpl.java:338)
         at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:54)
         at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)
    |#]

    PaulPeters wrote:
    The particular Page Flow instance has remained active for some reason and just timed out in accordance to the settings for eInsight on the Integration Server's section.
    Does the Page Flow start with an Event-Based Decision ? There's a small reference to that in the User Guide, but quite important in real-life.
    Do you implement time-out features inside the Page Flow ?Thanks for your reply.
    It happens after series of clicks. When I keep the app busy.
    My page flow looks like this:
    Event Based Decision, single link, continues with a while(true) loop, which contains everything else.
    JCD loads object from database, they are shown in a table with links (buttons styled as links) and some controls (pagination, but non jcaps, my own, and sorting)
    After click, the page flow continues to a detail page. From detail page you get back by a back button in browser. (Is this causing the problem?)
    After choosing the sort option or pagination, the page flow returns to the beginning of the while loop.
    I don't use any time-out features
    I've migrated the UI to another domain. The first domain runs a scheduled process. Now I don't get time outs. Maybe that was the problem. But the test team didn't test it thoroughly yet.

  • 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 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::
    * <!-- This data is auto-generated. Hand-editing this section is not recommended.
    -->
    * <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

  • 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 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

  • Stop sending us to the troubleshooting page, it doesn't work!!

    You can't keep sending thousands of people to the troubleshooting page because you
    know darn good and well it DOESN'T WORK! How about sending us a real fix???

    "we" send you an article because it is a starting point of reference to begin trial and error
    if manual and auto install of all Apple software does not work then heavier artillary.
    error messages etc
    And having been in the same boat, and I was using "Mint" for my iPod and their service is totally screwed up and that is my financial instution and I just don't want anything to do with Mint at this point.. I got boiling mad at them.... so I do know what it feels like.
    Okay. I can say that I had trouble with iOS and new iPod and found a PC hadn't used much that worked. I also tried clean installs on Windows 8 Preview just to see, and that works.
    apple is doing better but their 64-bit support and drivers/apps have not been that good even after 5 yrs? with Vista and counting, it now puts things "where they belong" better but the normal uninstall leaves behind old versions and files, so takes manual labor.
    And want to make sure you have been down that path.
    I spent a day on a new OS, pulled the old OS drive, been two years no real issues with Windows 7 until now, this and iOS.
    iTunes 10.5 does run better under Windows 8 Dev Preview than it ever did more me under 10.4 and Windows 7 (64-bit Pro SP1).
    Even a normal uninstall does not remove everything, and some things are in wrong location directories. Normally Apple leaves older versions around which never made sense and can interfere.
    Not just iTunes but ALL Apple software needs to be uninstalled and removed. Look for any Apple related and look for "Lockdown" and WOW64 if needed to find "Quicktime" remnants.
    https://support.apple.com/kb/HT1923

  • Include page flows into another page flow

    Hi,
    i have created two page flows that hit the database. i want create another pageflow that can call the two page flow i have created earlier.
    Any one please send me the docs on the eVision.
    Thanks,
    Krishna.

    http://docs.sun.com/app/docs/doc/819-6744?q=evision

  • Set data in page flow begin action?

    Hi,
    I want to set some data in my page flow's begin action, and then access this data in a JSP. In my begin method, I have:
    * @jpf:action
    * @jpf:forward name="index" path="index.jsp"
    protected Forward begin()
    getRequest().setAttribute("foo", "mydata");
    return new Forward("index");
    then, in my index.jsp, I have:
    <netui:label value="{request.foo}" />
    but the JSP is displaying an empty value (i.e., blank).
    Is there something about the page flow begin action such that this can't be done there?
    Thanks,
    Jim

    Hi,
    For my sanity's sake, I tried creating another small test web app in Workshop, and just added code to my begin action. This time, the display of {request.foo} worked.
    So, it looks like there is SOMETHING in my original web app that is causing the data binding to stop working.
    I've been comparing the small test web app to my original web app, and the only thing that is significantly different is at the beginning of the JPF, I have the declaration for a control:
    public class Controller extends PageFlowController
    * @common:control
    * @jc:ManualConfiguration UserIdAttribute="uid" UserBaseDN="dc=whatever,dc=com" Port="389" Host="foo.whatever.com"
    private AccountManager accountManager;
    * @jpf:action
    * @jpf:forward name="index" path="index.jsp"
    protected Forward begin()
    getRequest().setAttribute("foo", "foodata");
    return new Forward("index");
    Would having that control declaration before the begin() method be causing this problem?
    Any other ideas about why this might be happening?
    Thanks,
    Jim

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

  • Weblogic portal page flow issue

    Hi,
    We are working with portal development using legacy product. This runs on weblogic portal 8.1 SP 4.
    Part of the project, we have to provide user management. We are planning to use the java page flow offered by weblogic.
    When we create a new application and new project and try to create a new page flow (with the UserManager controller) standalone, it works.
    We access the legacy portlets by IMPORTING it as a project inside weblogic portal (i.e workshop). If we follow the same steps to create the page controller in this imported project, the page flow does not work. i.e., instead of displaying the form, it generates java code in the test browser of Workshop
    Do we have to enable any project specific settings for jpf to work.
    regards
    -Ramudu

    Hi,
    Proliferation refers to the process by which changes made to the Library instance of a portal asset are pushed into user-customized instances of that asset which means that when any changes are made to the portlet in source and if you want to propagate that change to the destination, that time if that portlet is used in a desktop where many users are provided an option to customize that desktop only that particular time at destination if you change the Portal Resources Proliferation of Updates Configuration setting to either Asynchronous or off propagation will be faster because that time propagation utility will not change for each user. If the value is synchronous it changes for each user and hence some delay that too it will happen during commit operation only but not during download operation.
    So I feel, Proliferation may not be useful for your case.
    We need to find why downloading source is taking 3 hrs and destination is taking 8 hrs.
    Please let me know whether you are running downloadsource and downloaddestination.
    I suggest run downloadSource in source machine itself and downloadDestination on the destination Machine itself so that you can reduce the network latency.
    Thanks & Regards,
    Murali.
    ===========

  • Unexpected error present when getting into the Troubleshooting page

    Hi, I'd like to figure out what's happening with my WRT1900AC, as well as with my Smart Wi-Fi App (version 1.7) . There is always an unexpected error present when getting into the Troubleshooting page. It would be appreciated if you have any suggestions for fixing that. Below is about my mention. Thank you!1. The firmware in my WRT1900AC.2. Steps to see an unexpected error with Smart Wi-Fi App.

    @angus19 Power cycle the router. You may also try to access your Linksys Smart Wi-Fi account using a browser and check if you’re getting the same error message. If all else fails, reset and reconfigure the router.

  • No header/footer in page flow JSP

    good morning group
    i have a jsp in a popup which is part of a page flow, and therefore, the html header & footer is displayed. is there a way to suppress the rendering of the header&footer stuff ?
    many thanx in advance :-)
    best wishes
    -ToM-

    "Mindy" <[email protected]> wrote in message
              news:402a4528$[email protected]..
              >
              > Is there a way to get the NT login name of a user in the page flows and
              jsp? We
              > want to authenticate a user belongs to a group before giving him access to
              a site
              > so the first thing in the begin method in page flow will be to get his
              login name
              > and then we have another module which validates the user belongs to a
              particular
              > group.
              Two possibilities spring to mind, NTRealm which is a security realm for
              weblogic that works with NTLM, I have no personal experience with it however
              you can search edocs for more info about it. Another alternative is jCIFS
              which includes an NTLM authentication handler for HTTP. I have used this in
              a previous life and it works great. You can view more info about it here
              http://jcifs.samba.org/src/docs/httpclient.html.
              Gerald
              

Maybe you are looking for