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

Similar Messages

  • 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

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

  • How to show  an error Page in Weblogic when the server is down

    Hi ,
    I heard that every container has the facility to show an error page when the server is down and (when the request has arrived at that time ).
    Please tell me how to configure this in BEA weblogic ??
    Thanks .

    Hi,
    From my understanding weblogic dose not provide the thing which you are asking for, reason is given below.
    - An application is deployed only on managed server one (MS-1)
    - Now if the request comes to the server (MS-1) when it was running and then for some reason MS-1 goes down then weblogic server would be able to send any response back to the client as its down.
    - Hence nothing can be done as the request object is been lost when the server goes down or even cant redirect to an error page as for doing that too the server has to be up and running.
    However there are other way round which can help you overcome this issue as shown below
    - Use Clusters with few managed servers in it which gives you high availability and load-balancing.
    - Use any web servers like Apache in front of weblogic servers.
    Using the above things you can also use customized HTTP Error Responses with error-page element in web.xml and create your own error pages which can be re-directed for the web server side also. For more information go through the below links
    Topic: Customizing HTTP Error Responses
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webapp/configurejsp.html#wp157884
    Topic: error-page
    http://download.oracle.com/docs/cd/E13222_01/wls/docs81/webapp/web_xml.html#1017571
    Topic: ErrorPage
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1155425
    Hope above information helps you.
    Regards,
    Ravish

  • Error pages in Weblogic 10.3

    I have no problem with error pages by error-type defined in web.xml, but by exception-type does not seem to work. Are there any additinal steps in this configuration?

        <error-page>
            <exception-type>java.lang.Exception</exception-type>
            <location>/Error.jsp</location>
        </error-page>   and in Error.jsp add,
    <%@ page isErrorPage="true" %>
    <html>
    <head>
    <title>Exception occurred</title>
    </head>
    <body>
    <%= exception.toString() %>
    </body>
    </html>

  • WebLogic Error Pages

    How can you replace the default WebLogic generated error pages (401,403,500) with custom error pages for all deployed applications?
    WL 10.3.3
    Edited by: SK Jennings on Oct 26, 2010 12:24 PM

    Hi,
    May be the following link would answer your question
    Re: How to show  an error Page in Weblogic when the server is down
    Hope this helps you.
    Regards,
    Ravish Mody

  • 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

  • Custom HTTP error page

    How do I create custom HTTP error pages for WebLogic Server 6.1
              

    Refer to the following document:
              http://e-docs.bea.com/wls/docs61/webapp/components.html#101747
              Eric
              "Sejal" <[email protected]> wrote in message
              news:3bc1e18f$[email protected]..
              > How do I create custom HTTP error pages for WebLogic Server 6.1
              

  • 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

  • Oracle WebLogic Portal 10.3.6: Creating a Java Page Flow Portlet in WorkShop

    Hello,
    We are not able to create a Java Page Flow Portlet in WorkShop. While adding the Beehive NetUI Facet(1.0.2) getting the following error in the workshop.
    error installing beehive netui facet
    File template generation failed: Unable to configure AvalonLogSystem : java.io.FileNotFoundException: C:\Windows\System32\velocity.log (Access is denied)
    Following are the environment details:
    WebLogic Server 11gR1
    Oracle WebLogic Portal 10.3.6
    Any Solution for this issue??

    Hi Chris,
    I have already gone through this document. But the procedure that is given in it is not working. I mean I am not able to render diffferent different jspx files based on the menu link clicked. It will great if you can provide me steps by step process since I am new to the portal World.
    Thanks a lot for your reply

  • Page Flow Portability kit incompatible with weblogic 7?

    I have a client who needs us to develop a web app to deploy on weblogic 7.
    I have been looking at the page flow that comes with weblogic 8, and that would
    be great if I could deploy it to weblogic 7.
    Therefore, I've been looking into the page flow portability kit, with the intention
    of deploying it and my application to weblogic 7 as per the instructions on http://dev-test.bea.com:90/technologies/standards/standards_pageflow_portability_index.jsp
    If I compile my pageflow app written on weblogic workshop 8.1, using jdk131, I
    get a
    java.lang.UnsupportedClassVersionError: com/bea/wlw/netui/xdoclet/NetuiDocletTask
    (Unsupported major.minor version 48.0)
    error. If I compile against jdk141, it works fine. However, if I try to deploy
    the jdk141 compiled version against weblogic 7 (which uses jdk131), then I get
    the following error:
    java.lang.UnsupportedClassVersionError: com/bea/wlw/netui/pageflow/PageFlowActionServlet
    (Unsupported major.minor version 48.0)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:802)
    Any ideas how I can get around this? I can't change my client's version of weblogic.
    Thanks.

    Hi,
    I just tested the downlaod url at http://dev2dev.bea.com/pub/a/2004/02/pgflow_portability.html#download and was able to download both the Tomcat version and the J2EE compliant version
    can you try again ?
    cheers
    Raj

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

  • How do I create custom HTTP Error Pages for a Weblogic Server

    I need to be able to display custom HTTP error pages such as a 404 from my Weblogic
    Server when my web application is not deployed.
    Is this possible?
    I have seen some suggestions about putting something like:
    <error-page>
    <error-code>404</error-code>
    <location>Error404.jsp</location>
    </error-page>
    in the web.xml for my web application but I can't see how that would work since
    the web application would not be deployed. I need to set these messages at the
    server level.
    Any help would be appreciated!
    thanks

    Your CategoryAxis id="ha_ccm" uses categoryField="period", and this is the label for the your series (i.e. "Quarter 4/2010"). You cannot have multiple categoryFields for the CategoryAxis; it can only use one data field for the labels. You can use data tips and/or label functions to show the individual series' values on the columns.
    Also:
    Your labelField in the ColumnSeries are set to a ColumnSet name instead of a field name in your dataprovider.
    Font must be embedded if you set ColumnChart.showLabelVertically="true".

  • 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

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

Maybe you are looking for

  • Problem with XML signature

    Can anybody tell me how to generate an xml signature with the base 64 transform(Transform.BASE64)? I just can't find any documentation on the web. It would be great to provide a small code exemple. Thanks Antoine

  • Add a formula in HFR

    Hello all.. We created reports in Hfr studio. now i need to add a column where in it should display the difference in value of the other two columns prior to it. we inserted column for formula. after selecting the column and custom function : in the

  • Get the id or namespace of  container of ADF Task flow

    Hi, I have an ADF Task flow and I put it inside either a region in a jspx page or portlet page. And I want to refer to the component in the adf page fragment in javascript by its id. How do I dynamically detect the id of the container of the ADF task

  • White flare/stripe on photos from direct light source

    I have a problem very similar to this https://talk.sonymobile.com/t5/Xperia-Z3-Z3-Dual/White-stripe-on-photos/td-p/909906 but i am not using flash. White stripe only shows when light is coming direct to camera from a light source like fluorecent lamp

  • DFF in Oracle Applications R12

    Hi, Can someone tell me what are the differences between DFFs in Oracle Apps 11i and R12?. Thanks, Renganayaki.