[jira] Created: (EXTSCRIPT-39) Add class dependency scanning and resolution
Add class dependency scanning and resolution Key: EXTSCRIPT-39 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-39 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Up until now we tried to resolve the dependencies via jsf artefacts, that only works out partially. Constructs like renderer which directly cast components in their code fail with this approach, a direct class dependency scanning system has to be added which can improve the currently implemented tainting algorithm, by also allowing to taint dependend classes on cast and import level, instead of plain jsf level. For the reload algorithms nothing changes, just the current tainting algorithm will be improved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-2454) Adapt default error page generation to new spec
[ https://issues.apache.org/jira/browse/MYFACES-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr updated MYFACES-2454: --- Status: Patch Available (was: Open) > Adapt default error page generation to new spec > --- > > Key: MYFACES-2454 > URL: https://issues.apache.org/jira/browse/MYFACES-2454 > Project: MyFaces Core > Issue Type: Task > Components: JSR-314 >Affects Versions: 2.0.0-alpha-2 >Reporter: Jakob Korherr > Attachments: myfaces-2454.patch > > > see spec section »6.2.3 Default Error Page« for details. > This includes the following tasks: > - should include the standard > error page (created by _ErrorPageWriter in MyFaces) in any facelet error page > defined in web.xml > - entries in web.xml should take priority over MyFaces' default > error page (currently you have to disable it via > org.apache.myfaces.ERROR_HANDLING first) > - UIInput should create an UpdateModelException and publish it, if an > exception occurs in updateModel() > - The error page should also include the view and the flash scope attributes -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: JSF [Trinidad] treetable, How to define Initially Selected Rows?
Majid,
Since you are using a ChildPropertyTreeModel, the keys are collections
of the Object where the Object is the key at each level.
Note that for performance, you are going to want to cache your
TreeModel someplace since it is likely that it will be accessed at
least once per phase and you don't want to recreate it each time.
-- Blake Sullivan
On Dec 18, 2009, at 2:25 AM, Majid Hussain wrote:
Hi,
My project is build in JSF, Hibernate and Faclets. i m using
trinidad treetable tag to build a tree with multiselection nodes.
Now i m facing a problem to initially selection of the nodes when
page is loaded at the first time. i have tried alot to accomplish
this task, but still unable to retain it. There is an attribute of
"selectedRowKeys" in TreeTable which takes the object of
"RowKeySet", but when i am building the tree in my bean, i don't
know the RowKeys generated, so how do i get my desired RowKeys to be
selected in the tree?
i am trying to provide the code below
myTree.xhtml
id="treeTableSelectButton" text="Submit Sel." action="#
{RoleManageBean.treeTableSelect}" />
MyBean.java
public class RoleManageBean implements Serializable {
private TreeModel tree;
private RowKeySet selectedRowKeys = null;
public TreeModel getTree() throws Exception {
Application[] applications = dbops.getAllApplications();
List empty1 = Collections.emptyList();
List root1 = new ArrayList();
List apps = new ArrayList();
for (Application application : applications) {
Set appPages =
application.getApplicationPage();
List pages = new ArrayList();
for (ApplicationPage applicationPage : appPages) {
pages.add(new Node1(applicationPage.getPageName(),
String.valueOf(applicationPage.getPageID()), empty1));
}
apps.add(new Node1(application.getApplicationName(),
String.valueOf(application.getHomePage().getPageID()), pages));
}
root1.add(new Node1("Applications", "0", apps));
tree = new ChildPropertyTreeModel(root1, "children");
return tree;
}
public RowKeySet getSelectedRowKeys() {
selectedRowKeys = new RowKeySetImpl();
selectedRowKeys.add(String.valueOf("1,0"));
System.out.println("called");
return selectedRowKeys;
}
public void setSelectedRowKeys(RowKeySet selectedRowKeys) {
this.selectedRowKeys = selectedRowKeys;
}
Any guideline will be appriciated. Thanks in Advance
Majid.
JSF [Trinidad] treetable, How to define Initially Selected Rows?
Hi,
My project is build in JSF, Hibernate and Faclets. i m using trinidad
treetable tag to build a tree with multiselection nodes. Now i m facing a
problem to initially selection of the nodes when page is loaded at the first
time. i have tried alot to accomplish this task, but still unable to retain
it. There is an attribute of "selectedRowKeys" in TreeTable which takes the
object of "RowKeySet", but when i am building the tree in my bean, i don't
know the RowKeys generated, so how do i get my desired RowKeys to be
selected in the tree?
i am trying to provide the code below
myTree.xhtml
MyBean.java
public class RoleManageBean implements Serializable {
private TreeModel tree;
private RowKeySet selectedRowKeys = null;
public TreeModel getTree() throws Exception {
Application[] applications = dbops.getAllApplications();
List empty1 = Collections.emptyList();
List root1 = new ArrayList();
List apps = new ArrayList();
for (Application application : applications) {
Set appPages =
application.getApplicationPage();
List pages = new ArrayList();
for (ApplicationPage applicationPage : appPages) {
pages.add(new Node1(applicationPage.getPageName(),
String.valueOf(applicationPage.getPageID()), empty1));
}
apps.add(new Node1(application.getApplicationName(),
String.valueOf(application.getHomePage().getPageID()), pages));
}
root1.add(new Node1("Applications", "0", apps));
tree = new ChildPropertyTreeModel(root1, "children");
return tree;
}
public RowKeySet getSelectedRowKeys() {
selectedRowKeys = new RowKeySetImpl();
selectedRowKeys.add(String.valueOf("1,0"));
System.out.println("called");
return selectedRowKeys;
}
public void setSelectedRowKeys(RowKeySet selectedRowKeys) {
this.selectedRowKeys = selectedRowKeys;
}
Any guideline will be appriciated. Thanks in Advance
Majid.
Re: [JSF 2.0] Moving ViewDeclairationLanguage Impl's to shared
+1 if it's about sharing the VDL base classes sharing is good. So you are basically suggesting to reuse the ViewDeclarationLanguage from MyFaces (including ViewDeclarationLanguageBase and ViewDeclarationLanguageStrategy) and make them part of the shared project ? -Matthias
AW: [ANNOUNCE] release of myfaces orchestra 1.4
Great to see a new release!! :-) Thanks Leonardo! Von: Leonardo Uribe [mailto:lu4...@gmail.com] Gesendet: Samstag, 19. Dezember 2009 01:09 An: annou...@apache.org; annou...@myfaces.apache.org Cc: MyFaces Development; MyFaces Discussion Betreff: [ANNOUNCE] release of myfaces orchestra 1.4 The Apache MyFaces team is pleased to announce the release of Apache MyFaces Orchestra Core 1.4 This release add support for portlets and new modules for compile orchestra with jsf 1.2 and 2.0 implementations. Also, orchestra core15 was merged in orchestra core module, because JDK 1.4 has reached its End of Life. Get a full overview at Orchestra's homepage [1]. The release notes for 1.4 can be found here: * http://svn.apache.org/repos/asf/myfaces/orchestra/tags/core-1_4/RELEASE-NOTE S.txt The distribution is available at * http://myfaces.apache.org/orchestra/download.html Apache MyFaces Orchestra is available in the central Maven repository under Group ID "org.apache.myfaces.orchestra". Regards, Leonardo Uribe [1] http://myfaces.apache.org/orchestra smime.p7s Description: S/MIME cryptographic signature
Re: [JSF 2.0] Moving ViewDeclairationLanguage Impl's to shared
Sent from my iPod. On 19.12.2009, at 03:30, "Scott O'Bryan" wrote: > > As for the VDL, simply put the current JSP VDL casts to some servlet objects > (at least in the R.I.) to do some things. ;) ClassCastExceptions do > not an effective bridge make.. Not to surprised if myfaces does that too. Filing bugs is welcome. Note that Apache MyFaces 2.0 is already alpha and we are not too far away from a real release... LOL. Yeah I know. I may have something very soon. If not then the bridge should be able to replace this code and use a later version.. ;) > > The current bridge overrides the ViewHandler.renderView to overcome this > problem, but I thought it might be nice to synchronize some code up. As it > is right now, I'm merging the code from the ViewHandler.renderView in the > Portlet 2.0 bridge with the current R.I. There are some strange issues > which I'm overcoming, but evenutally it might be nice to allow MyFaces > development to continue to drive these view handlers. sharing is good. So you are basically suggesting to reuse the ViewDeclarationLanguage from MyFaces (including ViewDeclarationLanguageBase and ViewDeclarationLanguageStrategy) and make them part of the shared project ? Yeah... Essentially I would take those objects in myfaces and allow them to have plugable Request/Response implementations. Then for the portal bridge, I would use the ViewDeclarationLanguageStrategies with the Portlet implementation pieces plugged in and MyFaces would have the servlet pieces plugged in. +1 on that Scott
