This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 231746 - Add support for PrimeFaces "outcome" attribute
Summary: Add support for PrimeFaces "outcome" attribute
Status: NEW
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 7.4
Hardware: All All
: P2 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-24 23:53 UTC by ecerichter
Modified: 2013-06-25 07:12 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ecerichter 2013-06-24 23:53:22 UTC 
Product Version = NetBeans IDE Dev (Build 201306232301)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_21
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.21-b01

When working in faces-config pageflow designer, I would like to see the "outcome" attributes from PrimeFaces as candidate for outcome in faces-config designer.
That will make easier for the developer to link the outcomes with destination pages.

Regards,

Edson
Comment 1 Martin Fousek 2013-06-25 07:12:17 UTC 
Thanks Edson for reporting but I'm afraid that we are not going to invest time into the pageflow. Beside the fact that the pageflow is not even JSF2.0 ready now, there would raise many questions like clashing xml/xhtml navigation rules, how to create new one, whether it should be available as the tab of faces-config since it's only optional config file... Probably we could think about switching such a flow into read-only view which would be available as a JSF project action and show something like navigation summary but hard to say whether this is possible to do.