Problem with rendered attribute in jhs 10.1.3.3

We are currently trying to migrate our applications from jhs 10.1.3.2.52 to jhs 10.1.3.3.87 using jdeveloper 10.1.3.5. We are facing a problem with all the detail groups structured inside detail group regions - they have all disappear from the pages.
In my example code i have two master-detail groups Products (Master) and ExpertiseAreas (Detail) on the same page:
Products - Group
-> ExpertiseAreasDtl - Detail Group Region
-> ExpertiseAreas - Group (Samepage="true")
The problem is that the detail group ExpertiseAreas is not rendered on the page.
As i looked in through the pages generated by the 2 different releases of jhs using the same app definition, i can see the following:
CODE GENERATED FOR THE ExpertiseAreasDtl Detail Group Region (all the vms used are the default):
in jhs10.1.3.3.87:
<af:panelGroup *rendered="#{(ProductsIterator.currentRow!=null and ProductsIterator.findMode!='true')}"* id="ProductsRegionsExpertiseAreasDtlPanelGroup">
in *jhs 10.1.3.2. 52*:
<af:panelGroup id="ProductsRegionsExpertiseAreasDtlPanelGroup">
First of all a rendered attribute is being generated in the new version of jhs and not in the old.
The real problem seems to be with the iterator binding generated from verticalRegionContainer.vm in the regular expression: "#{(ProductsIterator.currentRow!=null and ProductsIterator.findMode!='true')}". It should have been *bindings.*ProductsIterator and not plain ProductsIterator. Has anybody got any ideas on how to solve the problem?
Thanks
Giorgos
Edited by: user647567 on 17 Δεκ 2009 2:16 πμ
Edited by: user647567 on 17 Δεκ 2009 5:58 πμ

Giorgos,
We have uploaded a new service update, 10.1.3.3.88, on the cso.oracle.com site. This should fix your issue.
Steven Davelaar,
JHeadstart Team.

Similar Messages

Problem with rerendering h:panelGrid with rendered attribute

Hi,
I am new to jsf and trying to learn its features as I find it easy and fast for development purpose.I have been developing with jsf for past few weeks and got myself stuck with a problem, tired of which I had to take the forum's help :). My problem is that I need to show/hide h:panelGrid using any of the options below:
I tried putting the grid in the div and show/hide that div using javascript..works fine but the problem with this is, even when the div is hidden the components (h:inputText ) within the grid are submitted with the form, which should not be the case since its hidden (as with normal jsps).
I worked around with rendered attribute of the grid, and show/hide this grid using the backing bean method which is actually a valueChangeListener of h:selectOneMenu and set the boolean for the rendered to true/false as required, the grid is hide/shown correctly, but this isn't giving me any solution because when I submit the form with this grid shown on the view, its components values are still not submitted :( I dont know whats the reason behind this or what clue am I missing here. I dont know why when the grid is shown correclty, its components values are not submitted.. hence not validated too..
Any help will be highly appreciable.
Regards
srehman

>
gimbal2 wrote:
No, in "normal jsps" you'll get the same thing - even though you
visibly hide a component, it is still there and thus will still be part
of a form submit. If you don't want form fields to submit, you'll have
to make sure they are physically not there, or the fields are disabled.Well thanks alot for correcting me on this mate.
Don't know either, it should work if you did everything correctly. Are
you sure the databinding (to a JSF backing bean field) of the grid is
correct? When you create a similar setup but without any of the
show/hide logic, does it work then?I guess I have done it correctly but let me tell you, I have no direct binding to the grid itself, instead I have h:inputText fields in the grid that are bound to the backing bean's properties, which I need to submit and validate too. e.g{color:#800000}<h:panelGrid id="myPanel" columns="3" rendered="Bean.renderStatus">
<h:outputText value="variable"/>
<h:inputText id="v" value="Bean.property" required="true">
<a4j:support ......... />
</h:inputText>
</h:panelGrid>{color}
{color:#800000}<rich:message for="v"/>{color}
Here I am able to hide and show the grid but I am unable to submit the field in any case whether its hidden or shown :( At first the grid is hidden and then on the valueChangeListener of h:selectOneMenu rendered value is set to either true or false.( renderStatus is set in the value change listener ).
And yeah without this logic of hide/show its working fine with me. Any guess or idea what am I doing wrong here.
Thanks for your time by the way.
Regards,
Shoaib

Problem with optional attribute caching on a custom tag

Hello,
I've created a tag by extending TagSupport. I have one attribute that is optional. I'm having a problem with this attribute since the tag is cached. If the value is not specified in the tag, it is always using the previous value from the past request.
I understand why this is happening, but I wonder if there is anyway to reset this value besides doing it at the end of the doStartTag or in the doEndTag methods? I simply want it to be an empty string if it is not in the request.
Thanks,
Tim

Thats abit overkill in my opinion.Probably yes, but its a cleaner option. In case your doEndTag handles custom exceptions, you would anyhow need to put this code in a finally block, right ?
public int doEndTag() throws JspException {
try {
call some methods that throws other checked exceptions;
}catch(Exception1 e){
throw JspException(e);
}catch(Exception2 e){
//log and ignore
}finally{
//clean up here
return an int;
Having said that, different containers implement the spec a bit differently. For example, in our project, we use weblogic and for wl, we put our clean up code in the release() method which according to the spec, needs to be called only before gc. Weblogic implementation is a bit different - its called after doEnd() for every use of the tag.
This is from jsp spec regarding tag life cycle especially with reuse
Some setters may be called again before a tag handler is reused. For
instance, setParent() is called if it�s reused within the same page but at a dif-ferent
level, setPageContext() is called if it�s used in another page, and
attribute setters are called if the values differ or are expressed as request-time
attribute values.
�Check the TryCatchFinally interface for additional details related to exception handling and resource management.
cheers,
ram.
}

Very urgent : Problem with field attributes in Datasource

Hi
I am getting a problem with field attributes in the datasource.
The issue came up after i modified the extract structure-i modified one field and
added one field to the structure.Now those two fields are not visible in BW.
When i checked with transaction rsa2, i could find that for those two fields , the
field attribute is <b>'A'</b> which is <b>'Field in OLTP and BW Hidden by SAP'</b>.
I tried to modify the field attribute to make it visible.Now the issue is that it is not getting reflected after transport in the Q system.What can be the issue.In the Q system its still the old value 'A' ,which makes the fields invisible.
Please let me know what can be the issue.
Regards
Leon

Hi,
did you change this attribute via RSA2?
you need to change your datasource via postprocessing (RSA6); then transport your DS to your Q source system.
Replicate your datasources in your BW.
Finally modifiy your Transfer Structure by editing your TRules ( tab Datasource/Tran structure), move your new fields from the right frame to the left frame)
Maintain your TRules
Activate
hope this helps...
Olivier.

Problems with rendering quality in Premiere Elements 9

Hello, I've made a few videos with PE 9 now, and I get very poor quality rendering despite trying several different settings. I saw on a help thread earlier that I needed to try changing to HD when creating the new file from the beginning. I did that, but it only made my PE 9 run more slowly, and the rendering quality was not improved. I also read somewhere that using .MOV files as a source can cause problems with rendering; is that true? I hope not! I use a Lumix bridge camera for my videos, and the video quality is very good. And when I'm working with these videos within PE 9 the quality is great. It's only when exporting to various file types that the quality suddenly becomes poor. For the most part I have made compilation videos of gymnasts, and when their legs move they are often so lined or pixelated that they become invisible. Here is an example of a short gym video I made yesterday: http://www.youtube.com/watch?v=-0s7tUBcSZk. The last girl jumping gives the best example of this invisible leg problem.
You can see the original source films here: http://www.youtube.com/watch?v=zmUMi9oN8dQ
http://www.youtube.com/watch?v=OEzcJZjhxiI
and http://www.youtube.com/watch?v=I53twqPQMV4
The sequences I took in my compilation video start at about 20 seconds in the source videos.
Youtube does reduce the quality of the videos slightly, but in any case you can definitely see a difference in quality between the source videos and the PE 9 rendered compilation video.
I'm quite disappointed because I made a longer compilation video set to music (which was a lot of work), and it looks so much nicer on PE 9 than on any of the rendered formats, but of course I can't share the PE 9 version!
Thanks very much for your help.
Chleste

Thanks Steve. I'm not sure what resolution I'm shooting in, actually. However, the thing is that when I make these compilations, I like to go back to source videos I've made in the past sometimes. Sometimes these videos come from a Canon camera, and sometimes they even come from my Samsung mobile telephone. I like being able to creatively combine historic moments, and these moments might have been recorded without any intention at the time of making a compilation video. Is it not possible to combine several kinds of video sources?
I'm uploading an example of a compilation with mixed source videos from various kinds of cameras. It's 710 Megs so it will take a while, but when it's finished you will be able to see it at http://youtu.be/CslpULRe4LU.
I opened up the file for the compilation of the four girls on the beam (video posted in original message), and I do indeed see those red lines in the timeline. Is there anything I can do now about that, or do I have to start the project all over?
I'm confused about the processor requirements. Even if I can see my video perfectly in PE 9, the actual export process will be affected if my system is not up to par? If so, that's a bit disappointing! I'm not sure what my processor details are, but I will find out and let you know.
Many thanks.

Problem with rendered tables in JHeadstart 10.1.3.3.87

Hi,
We have recently upgraded from Jhs 10.1.3.3.52 to 10.1.3.3.87 (using JDev 10.1.3.4.0.4270) and have run into a problem with a window using regions. We have horizontal region containers, vertical region containers, stacked region containers and detail group regions. The tables in these containers/regions are not rendering at all. When I compared the .jspx pages of both versions of Jhs I noticed the 10.1.3.3.52 version had the following code (which works) as
<af:panelGroup rendered="#{(bindings.AwardView1Iterator.*currentRowIndexInRange!=-1* and bindings.AwardView1Iterator.findMode!='true')}" id="AwardView1DetailGroupsBelow" partialTriggers="AwardView1Table">
and the 10.1.3.3.87 version had the following code as
<af:panelGroup rendered="#{(bindings.AwardView1Iterator.*currentRow!=null* and bindings.AwardView1Iterator.findMode!='true')}" id="AwardView1DetailGroupsBelow" partialTriggers="AwardView1Table">
the problem seems to be in the following line in the horizontalRegionContainer.vm and stackedRegionContainer.vm -
#JHS_PROP("rendered" $subRegion.rendered)
as in line 33 of the horizontalRegionContainer.vm - <af:panelGroup #REGION_PARTIAL_TRIGGERS($subRegion) *#JHS_PROP("rendered" $subRegion.rendered)* id="#REGION_ID()${subRegion.name}PanelGroup" and
as in line 32 of the stackedRegionContainer.vm - <af:showDetailItem text="#REGION_TITLE($subRegion)" *#JHS_PROP("rendered" $subRegion.rendered)* #JHS_PROP("disabled" $subRegion.disabled) #REGION_PARTIAL_TRIGGERS($subRegion) id="#REGION_ID()${subRegion.name}Tab">
has anyone run into a similar problem?
thanks,
Lana

Thanks Steven!
We appreciate the reply and this solution. Could you, or anyone, point us in the direction of helpful documentation with respect to Velocity Templates. We don't really have as good an understanding as we would like, and most of our customizations are our best guess.
Thanks very much.
MaryB
U of Windsor

Value binding not working with rendered attribute

In my jsf page i'm encountering problem with value binding it is not working for a h:inputText with rendered condition even when the rendered condition evaluates to true & the component is rendered.While trying to retrieve the value of the components with conditional rendering on submit i'm unable to retreive the value while on removing rendered condition the value binding is working perfectly
<h:selectOneMenu id="DropDown" value="#pc_GeneralRequestInfo.objInfoDTO.State}" rendered="#pc_GeneralRequestInfo.objAddressRequestDetailsDTO.selectedAddressType == 'HOME'}">
<f:selectItems value="#{pc_GeneralRequestInfo.statesList}" />
</h:selectOneMenu>

There is a { missing from the value attribute in the code you posted.

CommandLink doesn't work with rendered-attribute

Hello,
I have quite a strange problem.
I have a commanLink, which has a rendered attribute. The link is rendered conditionally, so the rendered-value comes from a bean.
<h:commandLink rendered="#{Bean.canEdit}" action="#{Bean.selectDocumentToEdit}" >
<h:outputText value="Edit doc" />
<f:param name="param" value="#{Bean.doc.id}"/>
</h:commandLink>Showing the link is working like it should, but commandLink is not working with this. When I change rendered="true", commandLink works ok. But now it doesn't call the commandLink action at all.
Any help would be appreciated

rendered="true", commandLink works ok. But now it
doesn't call the commandLink action at all.I meant it doesn't call the commandLink action method when retrieving rendered-value from bean.
I'm using RI 1.1.01

Having a problem with commandButton attribute when i am using it under tabl

Having a problem with {color:#800000}commandButton {color}{color:#339966}attribute {color}when i am using it under{color:#ff0000} table{color}
I am using a command button under a table.
here is the example
<h:dataTable value="#{wlmHandler.plexes.plexes}" var="{color:#ff0000}onePlex{color}" border="0" cellspacing="0" cellpadding="0" width="100%" border="0">
<h:column>
<h:panelGrid border="0" cellpadding="0" cellspacing="0" columns="5">
<h:commandButton action="" styleClass="tixbutton" value="#{labels.ADD}" onclick="#{onePlex.tran}"/>
<f:verbatim> </f:verbatim>
<h:commandButton action="#{createTransaction.transactionCommand}" styleClass="tixbutton"
value="#{labels.SUBMIT}" actionListener="#{createTransaction.processAction}">
<f:attribute name="dbName" value="#{wlmHandler.dbName}"/>
<f:attribute name="plexName" value="{color:#ff9900}#{onePlex.name}"{color}/>
</h:commandButton>
</h:panelGrid>
<h:/column>
</h:dataTable >
when i am using this plex name atribute it is giving nullPointerException
{color:#ff9900}this value #{onePlex.name} i cant able to access inside the command button{color}

balu i have tried by seeing u r blog.
this is my structure of tables
plexes (if i iterate plexes table gives plex object)
|
------ plex (plex table gives transaction object)
|
------transactions(transactions table gives transaction table)
|
here i will have a command link to this link i have to pass the plex name which
will come from
i tried in this command action with HTMLDataTable getRowData()
i am not getting the selected row data .i am downcasting this getRowData() to plex.

Custom tag with rendered attribute

Is it possible to create a custom tag that operates similar to a JSF tag with the rendered attribute? Wrapping output with c:if test="..." is not as nice as the JSF rendered option, but I don't want to use JSF for this particular project.
Edited by: black_lotus on Nov 23, 2007 12:13 PM

TLD File, per your previous recommendation:
<attribute>
     <name>disabled</name>
     <required>false</required>
     <rtexprvalue>true</rtexprvalue>
     <type>boolean</type>
</attribute>My Tag class (snippet):
public class ButtonTag extends TagSupport
private boolean disabled;
public ButtonTag() {}
public boolean isDisabled()
     return disabled;
public void setDisabled(boolean b)
    disabled = b;
}A sample of the jsp file invoking it:
<c:set var="result" value="${computedValue}"/>
<ltm:button disabled="${result}"/>Regardless of the value of result, ("true" or "false") it always passes false to the setDisabled method of the button tag class.

XSLT-problem with sequence attributes

Hi,
in my XSLT-program (i'm a real newbie!) i'm adding dynamically attributes and their values to a tag, by using the following code :
<SUPPLIER>
<xsl:attribute name="FUNLOC">
    <xsl:value-of select="SUPPLIER_FUNLOC" />
</xsl:attribute>
<xsl:attribute name="NAME">
    <xsl:value-of select="SUPPLIER_NAME" />
</xsl:attribute>
<xsl:attribute name="LOCATION">
    <xsl:value-of select="SUPPLIER_LOCATION" />
</xsl:attribute>
</SUPPLIER>
The problem is that the attributes in the resulting xml-file are alphabetically ordered. For instance :
<SUPPLIER FUNLOC="9522222" LOCATION="NL" NAME="Test vendor VMOI">
How can i arrange that the result of the xml-file is a sequence of entrance is taken, so
<SUPPLIER FUNLOC="9522222" NAME="Test vendor VMOI" LOCATION="NL" >
regards,
Hans
[email protected]

Hi Hans,
I think you're using ABAP-XSLT?!
If you do so, you can solve the sorting problem by using a 1:1 Message mapping after the ABAP-XSLT mapping. This resolves the problem that the nodes are not in the correct order.
In your interface mapping you have to configure 2 mappings:
1: ABAP-XSLT
2: Message mapping.
Of course this means that the total processing time increases a little bit.
I had the same problem with the sequence of my (ACC_DOCUMENT) idoc nodes, the ABAP-XSLT screwed up the idoc, but the 1:1 message mapping solved the problem.
Regards,
Mark

Problem with rendering my project

Hello,
today I tried to render my latest project in Premiere Pro CS6 to upload it to youtube. With an estimated file size of ~2 Gigabytes I started the rendering process and waited for it to finish (about 50 minutes).
After it had finished with rendering I checked the file and what I saw was a 35 Megabytes file with the worst video quality one can even imagine. What is wrong with my premiere pro -.-
I've put many time and effort in my project and now it doesn't render properly. The interesting thing is that the preview in the full resolution inside my premiere pro application looks way better than the rendering result. WTF!?
Later I tried the option "render workspace" which took just about the same time (about 50 minutes) and brought me 7 rendered video previews... summed up 40 Gigabytes.
I am like kinda mad and sad at the same time and really can't figure out what is wrong. Please help me.
Here are my Output settings:
H.264 codec
1920 * 1080
29,97 FPS
high profile and 5.1
Bitrate: I tried everything from 8 to 100 (output always about ~40 Megabytes)
maximum depth
and maximum render quality
Please mention it if you need more information about this as I will be happy to provide detailed information and excuse my bad english, it isn't my mother tongue.

Yeah, but as you could may imagine i watched the render result
I could just go ahead and render it in 240p same result... Its way off in points of quality even compared to the preview on the top right
I mean I am not using premiere pro for the first time and this is the first time that i have to encounter this kind of problem. maybe I should try to render some of my old projects to see if they too result in 45 Mb ****** videos.
Someone help me

Problem with keeping attributes updated

We have a problem with the server model in Designer.
We have made a E/R diagram and genereted it to a server model diagram. Afterwards we want to delete some attributes which we delete back in the E/R program. Then we make some new attributes instead and generate a new server model diagram but the attributes which we have deleted in the E/R diagram is still present in the new server model diagram. The new attributes are there too. It is like the server model diagram only updates the new attributes, but doesn't delete the old, wrong, attributes.
What can we do to solve the problem?

Hi,
DDT will modify the attributes values (datatype, size etc.) on the target tables.
DDT doesn't drop the column if its corresponding attribute is deleted in ERD.
However we can achieve this by deleting the table definition from DE and then executing the DDT on the new/modified Entity.
Regards,
Wilson.

Problem with rendering RGB with alpha

I have AE 6.5. I suddenly began having .AVI's with alpha channel rendering with a flickering background with numerous flashing colors.
I did system restore, reinstalled 6.5 with no help.
No new programs, not hooked to internet, using 2 gigs RAM with AMD athalon FX 53,Nvidia GeForce FX 5500.
I tried several different projects which have previously worked and they do the same thing.
Rendering as Video for Windows with no compression. RGB + Alpha
Rendering with just RGB doesn't have the flickering, etc.
Preview set to "off" in comp window.
Any help would be greatly appreciated.
Thanks in advance.
John Rich

> I have AE 6.5. I suddenly began having .AVI's with alpha channel rendering with a flickering background with numerous flashing colors.
But when you composite these lcips I'll bet the alpha content is not really there.
We used to have this problem with the Media 100 hardware codec when rendering form After Effects. The alpha channel was full of the creepiest stuff, frame buffers motion blur and effects from other compsand it was really there. Playing the clip back in Media 100 or in QT showed the alpha channel's bizarre content.
However, if you turned off RGB and viewed alpha only, the stuff was gone, absolutely transparent. If you dropped the clip into a timeline, the alpha behaved normally.
We never did figure it out, just lived with it.
bogiesan

Having problems with rendering clipls

I am new to Premier elements, and am having problems with my clips needing frequent rendering. Clips that have been rendered go from green (line) to red when a transition is added or if it is trimmed and must be rendered again. Also rendering seems to take a very long time, sometimes going fast, sometimes going a frame per second or slower. One possible problem is that I am mixing clips from two different cameras, one a HD and the other a standard def camera. I don't know if this is a factor or not.

If your clips are initially importing with a red line your project preset may be wrong - what preset are you using?
After applying transitions or effects it is normal for those segments to go red line.
It doesn't help to use two different types of video in one project. What is your final output intent - DVD or BluRay? If DVD then it would be better to convert your HD material to DV-AVI. See the Gspot link below - analyse both types of clip you are using and post the screen images here.
Some basics:
Install all Windows Updates.
Install latest version of Apple QuickTime (v7.6.7 at time of writing). Even if you don't use QuickTime, PRE relies heavily on it.
Install most recent graphics and sound drivers from the manufacturers web sites.
Run Disk Cleanup.
Run Defragmenter.
Temporarily disable any anti-virus realtime scanning.
Use the GSpot Codec Information Utility to analyse the file and post screen image.
Post back here with the necessary information described here: Got a Problem? How to Get Started
Cheers,
Neale
Insanity is hereditary, you get it from your children

Problem with rendered attribute in jhs 10.1.3.3

Similar Messages

Maybe you are looking for