Jheadstart 10.1.3.1.26: Tree Securitry

I have a master detail arrangement: MenuGroup and MenuDetail
I also use ADF security and granted access to the tree items to the appropriate roles.
Problem:
The master records display in the tree properly
The detail records show as nodes without labels (For example if there are 5 records, I get 5 rows without any value)
Jhedstart generates two pages: MenuGroup.jspx and MenuDetail.jspx. I set the appropriate authorization on all of them.
I also noticed that jhs generates a region definition page with out a page definition. Could the problem be in that page?
I appreciate any help in this regards.
Regards,
Ali

Ali,
"I also noticed that jhs generates a region definition page with out a page definition"
This is intended behavior, ADF FAces regions cannot have their own page definitions.
I suspect this to be an ADF issue. To verify, can you manually build a JSF Page with an ADF Faces tree based on the same data, with ADF security enabled, and see whether the tree renders correctly?
Steven Davelaar,
JHeadstart Team.

Similar Messages

Error when running a JHeadstart generated two-level tree display

Dear All,
I have a simple master detail VO/VO datamodel based on which I'd like to generate a two-level tree display. I've followed the JHeadstart dev guide meticulously.
When I run the page I get an error:
javax.faces.el.PropertyNotFoundException: Error getting property 'name' from bean of type oracle.jbo.uicli.binding.JUCtrlHierTypeBinding
It turns out that this generated code in a region file is the root cause:
<af:switcher facetName="#{node.hierType.name}">

<f:facet name="MutatieSoortTypenNode">
<af:outputText value="#{node.Omschrijving}"/> </f:facet>


<f:facet name="MutatieSoortenBijTypeNode">
<af:outputText value="#{node.Omschrijving}"/> </f:facet>

</af:switcher>
When I substituted the <af:switcher> .... </af:switcher> xml code by <af:outputText value="#{node.Omschrijving}"/>, the page displayed correctly.
Given the fact that the code is generated, there doesn't seem to be much that I can do about it.
We're using JDeveloper version 10.1.3.3.0 and JHeadstart version 10.1.3.2.41.
Any help or suggestion would be much appreciated.
Kind regards,
Ibrahim

Ibrahim,
I cannot reproduce this. You are using a non-production build. Can you upgrade to JHeadstart 10.1.3.2.52?
If the problem persists, you can work around it by creating a custom template for tree.vm which includes the af:switcher statement.
Steven Davelaar,
JHeadstart team.

Why not support tree/shuttle layers for Structs/JSP in jheadstart 10.1.2.0.

Why not support tree/shuttle layers for Structs/JSP in jheadstart 10.1.2.0.
I want make tree style and shuttle style with Structs/JSP(jheadstart 10.1.2.0) in my project.
Can you help me.
Thanks for your help.

UIX provides tree and shuttle components that generate all the complex javascript required for these UI component.
We have no plans to create similar javascript ourselves so we can generate this with JSP. The future strategy for JHeadstart will be based on JSF / ADF Faces where we leverage UI components that have this functionality built-in, like UIX has today. With the JSF standard out there, we expect lots of sophisticated new UI components to come out, built by dhtml/javascript/ajax experts (which we are not).
Our focus (and core competency) is on generating applications by wiring together these sophisticated UI components, and not so much on building new UI components.
If you want to build this today using JSP I suggest you do some shopping on the internet, you wll probably find some sample code for trees and shuttles.
Steven Davelaar,
JHeadstart Team.

Tree and JHeadstart

I'm trying to use JHeadstart classes to build the tree but I do not understand it. Has anyone used it? Can you publish some example.
Thanks Robert

Robert,
We are aware of the fact that the classes shipped with JHeadstart are not very easy to use. Unfortunately, we do not have a working example for you.
Within the next months we plan to create a tutorial on how to create a tree, but for now, you have to rely on fellow developers who found it out "the hard way".
Steven Davelaar
JHeadstart Team.

How to build a BIG TREE with Tree-Form layout

Hi,
I do have a self-referenced table with our org structure - 15 000 positions.
I do want to create a tree with this structure.
Requirements :
a, to have a tree-form layout
b, to have search capabilities
I have tried to use several combinations (maybe all)
- from using only one View object and create recursive tree - doesn't even run
- to use two View objects, first as top level nodes, the other as the rest - it runs
but I can search only top level, and what is worse, by clicking on the node for showing additional information (tree-form layout) I'm waiting for ages for seeing the info
(it seems that all records are loaded one by one into AS)
Could you provide some ideas how to deal with this ?
Thanks.

I am sorry, this is beyond the scope of this forum.
As with any functionality not directly provided by JHeadstart, you can build it yourself using the ADF design time tools in JDeveloper. Please use the JDeveloper forum for help on this first step.
Then, to keep your pages generatable you can move these customizations to custom templates. We are happy to help you with this last step, should you have problems there.
Steven Davelaar,
JHeadstart Team.

Problem to generate secret field with JHeadstart 10.1.3.1.0

Hi,
I'm experimentig the new version of Jheadstart and I have a problem to generate a JSF page with a secret field using the Oracle JHeadstart 10.1.3 Evaluation Version.
In fact when I change the display filed in the jheadstart Application Definition Editor to "secret" and then try to generate
jsf pages, i have this message error for both form and table layout :
Could not instantiate JhsApplicationGenerator class: No bean named 'secretPGItemModel' is defined:
org.springframework.beans.factory.xml.XmlBeanFactory defining beans [applicationLayoutGenerator,facesConfigGenerator,
regionMetaDataProcessor,includesGenerator,menuGenerator,nlsGenerator,pageGenerator,treeGenerator,generatorContext,findPageNameFormat,
findPage,wizardFindPage,formPageNameFormat,formPage,wizardFormPage,formRegionPage,wizardFormRegionPage,selectPageNameFormat,selectPage,
wizardSelectPage,treeFormPage,treePage,tablePageNameFormat,tablePage,wizardTablePage,lovTablePage,parentShuttlePage,
wizardParentShuttlePage,intersectionShuttlePage,wizardIntersectionShuttlePage,formPageComponent,tablePageComponent,
selectPageComponent,parentShuttlePageComponent,intersectionShuttlePageComponent,pgItemModelHelper,textInputPGItemModel,
dateFieldPGItemModel,dateTimeFieldPGItemModel,secretFieldPGItemModel,fileUploadPGItemModel,fileDownloadPGItemModel,imagePGItemModel,
editorPGItemModel,displayFieldPGItemModel,dropDownListPGItemModel,checkBoxPGItemModel,radio-verticalPGItemModel,
radio-horizontalPGItemModel,hiddenPGItemModel,lovPGItemModel,pgGroupModel,pgDynamicDomainModel,pgStaticDomainModel,
pgItemRegionModel,pgGroupRegionModel,stackedPGRegionContainerModel,separatePagesPGRegionContainerModel,horizontalPGRegionContainerModel,
verticalPGRegionContainerModel,searchManagedBeanModel,dependsOnItemManagedBeanModel,dependsOnSearchItemManagedBeanModel,
lovItemManagedBeanModel,lovItemInTableManagedBeanModel,editorItemManagedBeanModel,lovItemInAdvancedSearchManagedBeanModel,
lovItemInQuickSearchManagedBeanModel,lovPageManagedBeanModel,fileItemInTableManagedBeanModel,mediaItemInTableManagedBeanModel,
checkboxInTableManagedBeanModel,treeManagedBeanModel,parentShuttleManagedBeanModel,intersectionShuttleManagedBeanModel,
collectionModelManagedBeanModel,queryBindParamsManagedBeanModel,queryBindParamsDomainManagedBeanModel,defaultValuesManagedBeanModel,
wizardPageManagedBeanModel,wizardPageListManagedBeanModel,breadcrumbManagedBeanModel,customManagedBeanModel,velocityInitializer,
formGroupLayoutFactory,tableGroupLayoutFactory,table-formGroupLayoutFactory,select-formGroupLayoutFactory,tree-formGroupLayoutFactory,
treeGroupLayoutFactory,parent-shuttleGroupLayoutFactory,intersection-shuttleGroupLayoutFactory,
pgModelFactory,templateBindingsFactory,pgModelValidator]; root of BeanFactory hierarchy
My Jdeveloper Version is : 10.1.3.0.4 (SU5)
thanks

Steven
I followed your instructions and it works
I recently downloaded the production version of JDeveloper Studio Edition Version 10.1.3.1.0.3984
Build JDEVADF_10.1.3.1.0_NT_061009.1404.3984
I installed JHeadstart evaluation version.
I recreate the same example with this new version of JDeveloper
I found the bean definition in the jag-config.xml (by default)
I removed the "#ITEM_PARTIAL_TRIGGERS_PROP" from the template (default/item/form/formSecret.vm )
I thought it will work but unfortunately it doesn't work and and I got the same error
Could not instantiate JhsApplicationGenerator class: No bean named 'secretPGItemModel' is defined: org.springframework.beans.factory.xml.XmlBeanFactory defining beans [applicationLayoutGenerator,facesConfigGenerator,regionMetaDataProcessor,includesGenerator,menuGenerator,nlsGenerator,pageGenerator,treeGenerator,generatorContext,findPageNameFormat,findPage,wizardFindPage,formPageNameFormat,formPage,wizardFormPage,formRegionPage,wizardFormRegionPage,selectPageNameFormat,selectPage,wizardSelectPage,treeFormPage,treePage,tablePageNameFormat,tablePage,wizardTablePage,lovTablePage,parentShuttlePage,wizardParentShuttlePage,intersectionShuttlePage,wizardIntersectionShuttlePage,formPageComponent,tablePageComponent,selectPageComponent,parentShuttlePageComponent,intersectionShuttlePageComponent,pgItemModelHelper,textInputPGItemModel,dateFieldPGItemModel,dateTimeFieldPGItemModel,secretFieldPGItemModel,fileUploadPGItemModel,fileDownloadPGItemModel,imagePGItemModel,editorPGItemModel,displayFieldPGItemModel,dropDownListPGItemModel,checkBoxPGItemModel,radio-verticalPGItemModel,radio-horizontalPGItemModel,hiddenPGItemModel,lovPGItemModel,pgGroupModel,pgDynamicDomainModel,pgStaticDomainModel,pgItemRegionModel,pgGroupRegionModel,stackedPGRegionContainerModel,separatePagesPGRegionContainerModel,horizontalPGRegionContainerModel,verticalPGRegionContainerModel,searchManagedBeanModel,dependsOnItemManagedBeanModel,dependsOnSearchItemManagedBeanModel,lovItemManagedBeanModel,lovItemInTableManagedBeanModel,editorItemManagedBeanModel,lovItemInAdvancedSearchManagedBeanModel,lovItemInQuickSearchManagedBeanModel,lovPageManagedBeanModel,fileItemInTableManagedBeanModel,mediaItemInTableManagedBeanModel,checkboxInTableManagedBeanModel,treeManagedBeanModel,parentShuttleManagedBeanModel,intersectionShuttleManagedBeanModel,collectionModelManagedBeanModel,queryBindParamsManagedBeanModel,queryBindParamsDomainManagedBeanModel,defaultValuesManagedBeanModel,wizardPageManagedBeanModel,wizardPageListManagedBeanModel,breadcrumbManagedBeanModel,customManagedBeanModel,velocityInitializer,formGroupLayoutFactory,tableGroupLayoutFactory,table-formGroupLayoutFactory,select-formGroupLayoutFactory,tree-formGroupLayoutFactory,treeGroupLayoutFactory,parent-shuttleGroupLayoutFactory,intersection-shuttleGroupLayoutFactory,pgModelFactory,templateBindingsFactory,pgModelValidator]; root of BeanFactory hierarchy

Reference to parent record in Tree view

Dear Jheadstart Team,
When creating a Tree which I intend to use to insert child records, it is indeed possible to insert these records, unfortunately the key that identifies the relationship with the parent (in the child record) is always set to null and has to be inserted manually. How can I modify my application in order to let the application fill in the above specified value?
Kind regards

Double-click the Create button to create a managed bean method where you can add custom code after the new row has been created. In the custom code, you can set the parent key attribute.
Then move the new button code in the jspx page to a custom template.
Steven Davelaar,
JHeadstart Team.

How do we make a newly created tree-node the currently selected one?

Hi,
We are using JHeadstart 10.1.3 - Tree Generation. We are running into several issues with the trees, especially upon creation of new tree nodes. The Form in our Tree-Form page is Saved. At that point, we would like the new node to be the selected node in the tree (and also in the tree bean).
How do you believe can we do this? Right now, after creating the new node, we have no node selected - although it seems that the new node is selected as the normally synchronized form on the right shows that node.
Thanks for any suggestions!
Lucas

Steven,
I had not upgraded to Service Update 1 - was using Build 91. After upgrading, I see some difference, but not entirely the result I was looking for.
In a Tree-Form page on Employees, when I added an employee at the same level it still did not seem to be automatically selected.
Was wondering whether perhaps this has to do with the following comment from the source code:
          // this happens when posting back to the same node level in the tree:
          // the root node binding has no children in that case, causing derivation
          // of focus row key to fail, have to find out why root node children
          // are lost. Work around for now: return the focus row key as set by
          // the user clikcing on the nodeIf not, can you explain what this comment refers to?
thanks for your help.
Lucas

Editable Recursive Tree

hi evreyone
I need to create an editable tree based on (one table called Locations)
this is the structure of this table
LocationNo
LocationName
ParentLocationNo
LocationNo and ParentLocationNo are Forign keys
according to what I've red I should use a recursive tree (Self-Reference forign key)
using a view that represent the tree (nodes & branches)
how can I create this tree (with Details Steps) ?
I am using
Jdeveloper 11.1.1.2.0
JHeadstart 11.1.1.2.29
thanks

hi
According to chapter 5 "Creating Tree Layouts", 5.7.4 "Variation: Recursive Tree"
I've created a Recursive Tree based on table call (Location)
but the problem is how can I refresh the data ... I mean .. How can I See the new record that I've
created in the same tree without moving in it (to make a refresh)
thanks

Is treeTable supported with JHeadStart

Is ADF TreeTable component (<af:treeTable) supported when using JHeadstart.
If so how.
If not what is alternative to that?
Cheers,
Brij.

No, not supported with default generation.
You can create the tree-table with drag and drop, and if you wish to keep the page generatable, you can move the the tree table tag to a custom template, and uncheck the group-level property "Clear Bindings Before Generation" to preserve the tree table bindings in the page definition upon regeneration.
Steven Davelaar,
JHeadstart Team.

Tree Layout and a Where Clause

I have built a uix application using Jdev (10.1.2) + Jheadstart (10.1.2). I followed Jheadstart for ADF developers guide (10.1.2) for creating a page with a recursive tree, tree layout style and it works well. Now I need to apply a where clause, programmatically, on the view I am using for generating the tree and the problem is that the where clause 'gets lost' on the child view before the page is displayed. How do I fix this?

rbackmann wrote:
And the page_id_1 is a field in the table (SORRY EXAMPLE BAD NAMING CONVENTIONS) that IS VARCHAR
and houses a comma seperated list of page numbers ie 28,29, 30Okay, I was wrong about the field name :(
Carefully examine the query, expecially the INSTR line. Get the values in both the column and the bind variable and make sure they are what you think they are.
The example on the other post might have failed because you were equality comparing the column value to '28' when it might have been a csv with commas unless you changed it (something worth trying).
On 4th look I may (or may not) have something. PAGE_ID_1 is a VARCHAR2, while the 28 you compared it to was a number. Its a long shot, but maybe SQL is trying to convert the csv field to a number, failing to raise an error message where you can find it, and failing for that reason. Try using '28' on the equality test.
Edited by: riedelme on May 8, 2009 6:03 AM

Alternative approach to tree business model

Hi JHS Team,
When generating tree-forms with JHeadstart, we need two VO instances in the model for each node we want to present: one for rendering the Tree and another to show on the form, after the user selects a node.
I understand that this is necessary for the case when the user clicks on one node which father node isn't the current row of its corresponding View Object, and so in such case the form couldn't find the current row and show the correct data.
I'm still using the 10.1.2 version, but I checked the 10.1.3 documentation and this model requirement is still there.
I tried another approach to this issue, which consists of using the very same VO instance for trees and forms: in every level, I render the node with every Iterator used in the previous levels and each corresponding row key for every previous levels. When the user selects a node, in that node link I have every Iterator I need to seek and every primary key I need to search for, so I can really reconstruct the path used by the user to seek that node.
So, the benefit is that I don't need a root VO in the AM for every node I need to present as a form. In huge trees, this really simplifies the model construction and its maintanance.
In 10.1.2, the runtime library (JhsDataAction) is already prepared for this, so I would like to know, if possible, the reasons why this is not used already by default (maybe performance?). If there is a reason to mantain the two VO instances in 10.1.3, could it be changed to allow us use the same instances as an alternative to simplify models, and generate the JSF pages working accordingly?
Thanks a lot!
Eduardo

Hi Steven,
Many thanks for the explanation. I agree with you that the current implementation is easier to understand, but I think it is only from the point of view of a programmer who understand some concepts of ADF business model. When you're a beginner, it's more difficult and less intuitive (or at least it was for me some time ago :-))
I can say that in our project we have 4 very large trees in the same Application Module (since they need to be present on the same project as they're all related), and in each level we have at least 3 or 4 "details" VOs we present in the form, so the final model is really huge and really difficult to maintain. It was surprisingly easy to change the UIXs to the other approach, however, so I asked myself if this was tried already. Thanks for warning me of the unpredictable problems, I'll see if we have any.
Eduardo

Jheadstart, JDeveloper and CVS and TeamWork

Hi
We're four-developer team and we've been working with Jheadstart for some months. Now we want to work with team options that provide jdeveloper (CVS or SCM). But, we are a too much suprised with all the problems that other developers had with CVS, we read it in some jdeveloper forums (JDeveloper and CVS and TeamWork and JDeveloper and CVS
I get very worry about the problems that developers had with CVS and that at last they don't find a better solution than migrate to jdeveloper 10.1.3. All the forums recomend migrate to jdeveloper 10.1.3 for better support of team work, but I read (some time ago) that jdeveloper 10.1.3 still doesn't support ADF, then I assume we cannot use it with Jheadstart, Am I right? Is there a way to use Jheadstart with JDeveloper 10.1.3 Preview right now?
What do you recomend for team work with Jheadstart?
Thanks in advance
Liceth

Liceth,
As you problably know, the JHeadstart team consists of consultants and we face the exact same problems and share the exact same frustrations as you do on an every day basis at our customer projects. It is indeed not easy to use JDeveloper in a multi-developer environment. In all fairness much of this is a given when doing file-based development, and I have seen the exact same problems in situations where other IDE's such as Eclipse etc were used. But using advanced frameworks like ADF and BC4J makes matters more complex, because the declarative way of developing these applications using drag&drop and powerful wizards make you as a developer be less 'in touch' with the file or files that are actually created and updated, and also there tend to be more files in such an architecture that are changed simultaneously by many developers at once.
Merging is the only way out of this mess, and merge tools are not perfect, far from it. They get better and better but at some point you'll need to understand the semantics of the files that are to be merged to be able to merge them correctly, and merge tools will in all likelyhood never become that smart.
Until they do, the only thing one can do is to tackle the problem from the other side: if merge tools dont understand the files they merge, we should take into account the weaknesses of these merge tools, and set up our files so that changes CAN be automatically merged, or in most cases at least. Indeed, JDeveloper 10.1.3 is taking good steps in this direction for notoriously tricky files such as JPR files and such. But the problem will never completely go away.
As for using 10.1.3, well, as you said the preview does not contain ADF so JHeadstart will never run on it. We are developing JHeadstart 10.1.3 that will run on the production version of JDeveloper 10.1.3, but it will be a long time before that release will see the light. And although JDeveloper 10.1.3 is a kick-ass IDE (imho), it will not magically solve all multi-user issues. It will just be a bit more bearable.
Is there ever a real solution for it? I don't know. I have worked intensively with the Oracle Designer product before I switched to Java, and that tool, which uses a database rather than files to store its information, was almost perfect when dealing with multi-user development. It could do so because the level at which conflicts occur is VERY finegrained (so not at 'code line' level but sometimes as far as 'individual properties in a property inspector' level), plus the advantages of instantaneous locking in the database when modifying something. And, thinking of it, it could do so because it dealt with 'structured objects' rather than files, thereby having some 'semantic' information about the data. I have this feeling we can only 'get it right' if we will treat, for instance, a Java file not as a collection of lines of code, but of a structured object tree with members, constructors, methods, parameters etc. etc., and store it as such, instead of storing it as a flat OS file.
Just ranting here (this really should be a personal BLOG entry rather than a forum post, but oh well). As you can tell, its a subject that is very close to every developer's heart.
Kind regards,
Peter Ebell
JHeadstart Team

UIX tree, table-based example needed

Has anyone ever used the UIX tree element (JDev help, UIX developer's guide, chapter 15) in combination with BC4J and/or Jheadstart generated UIX-pages? Any examples are welcome. I also can't get the (static :-/) example in the Help to expand when clicking the +/- icons. Help on this one too please. Tnx.

You should try to post this question on JDevelper Forum.

11g's TREE PROBLEM

Hello,
I'm using Jeveloper11g TP1 and I need to know what should I do if I want to have 11g's tree be updated every time I add a new item in it? coz I see that it has to be requeried each time I add an Item in it.
Is there a way to see the added item in the tree right after pushing the save button??
Any idea what I'm missing?
Thanks Shadi

Shadi,
There are quite a few limitations with the tree implementation in TP1. I suggest you wait for the production version, planned for this fall to get this feature.
Steven Davelaar,
JHeadstart Team.

Jheadstart 10.1.3.1.26: Tree Securitry

Similar Messages

Maybe you are looking for