Re: [Tobago] renderedPartially doesn't work in treeNodeCommand
Hi Raj,
your code looks ok to me.
I suppose you're using Tobago 1.0.12 or later?
Have you tried it without mode="menu"?
When you look at the generated HTML you should see a line like this:
+ " var mainpage_nav_treeNodeCommand =
\"Tobago.reloadComponent('mainpage:rightPanel',this.id, {});\";"
What exactly happens when you click on a node? Just nothing?
Regards
Helmut
P.S. Please send requests like this to the mailing list. Maybe there're other
users who can help you or have a
similar problem.
- Original Message -
From: Raj .G. Narasimhan
To: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 5:37 AM
Subject: [Tobago] renderedPartially doesn't work in treeNodeCommand
Hi Bernd and Helmut:
I am writing to both of you, as this was the issue raised during mid of '07
on the subject issue. I'm experiencing the same issue, in the partial reloading
as Helmut had experienced. I'm trying to reload the detail page on click of
the tree node(s). I have a tree of around 300 nodes (Objects with 4-5 string
properties). I don't know, where and what I'm missing and I have been trying
to fix this since two days... Appreciate your help!
Here's the code, that I'm trying:
Here's the portion of main page (where this detail page will have to be
loaded)
..
<%--
--%>
.
--
Thanks,
Raj .G. Narasimhan
Re: [Tobago] renderedPartially doesn't work in treeNodeCommand
Hi,
just one idea: Does the action mainTree.showInDetail returns an outcome != null
?
If so the whole page gets reloaded.
Helmut
- Original Message -
From: Raj .G. Narasimhan
To: users@myfaces.apache.org
Sent: Wednesday, February 13, 2008 4:30 PM
Subject: [Tobago] renderedPartially doesn't work in treeNodeCommand
I'm having problem with partial reloading while invoking 'treeNodeCommand'.
I am using Tobago 1.0.14 on Tomcat 6.
On clicking the node link, the detail page including the tree gets reloaded,
even though the 's 'renderedPartially' value is set to body of the
page(showing the detailed node info). This issue was raised and resolved during
mid of '07(fixed in Tobago 1.0.12). This tree holds around 300 nodes (user
Objects with 4-5 string properties). I have tried without mode="menu" as
suggested by Helmut. Still the problem exists. I don't know, where and what I'm
missing and I have been trying to fix this since two days...
Here's the code, that I'm trying:
Here's the portion of main page (where this detail page will have to be
loaded)
..
<%--
--%>
.
And in the generated html source, I could see the following:
var mainpage_navigator_nav_treeNodeCommand =
\"Tobago.reloadComponent('mainpage:rightPanel',this.id, {});
Appreciate your help!
--
Thanks,
Raj .G. Narasimhan
[Tobago] renderedPartially doesn't work in treeNodeCommand
I'm having problem with partial reloading while invoking 'treeNodeCommand'.
I am using Tobago 1.0.14 on Tomcat 6.
On clicking the node link, the detail page including the tree gets reloaded,
even though the 's 'renderedPartially' value is set to body of
the page(showing the detailed node info). This issue was raised and resolved
during mid of '07(fixed in Tobago 1.0.12). This tree holds around 300 nodes
(user Objects with 4-5 string properties). I have tried without mode="menu"
as suggested by Helmut. Still the problem exists. I don't know, where and
what I'm missing and I have been trying to fix this since two days...
Here's the code, that I'm trying:
Here's the portion of main page (where this detail page will have to be
loaded)
..
<%--
--%>
.
And in the generated html source, I could see the following:
var mainpage_navigator_nav_treeNodeCommand = \"Tobago.reloadComponent
('mainpage:rightPanel',this.id, {});
Appreciate your help!
--
Thanks,
Raj .G. Narasimhan
Re: [Tobago] renderedPartially doesn't work in treeNodeCommand
Helmut, it does return "customer/custTabpane", which is the valid outcome to
be returnedand in fact, it loads the detail page also. Only issue, is
the tree is getting reloaded, (Moreover, this issue is more pronounce
because the tree's taking atleast 5-6 seconds to re-load ). The detail page
loads pretty quickly...compares to tree(and there's no need for the load to
be reloaded)
thanks,
Raj
On Feb 13, 2008 10:40 AM, Helmut Swaczinna <[EMAIL PROTECTED]> wrote:
> Hi,
>
> just one idea: Does the action mainTree.showInDetail returns an outcome !=
> null ?
> If so the whole page gets reloaded.
>
> Helmut
>
>
> - Original Message -
> *From:* Raj .G. Narasimhan <[EMAIL PROTECTED]>
> *To:* users@myfaces.apache.org
> *Sent:* Wednesday, February 13, 2008 4:30 PM
> *Subject:* [Tobago] renderedPartially doesn't work in treeNodeCommand
>
> I'm having problem with partial reloading while invoking
> 'treeNodeCommand'. I am using Tobago 1.0.14 on Tomcat 6.
>
> On clicking the node link, the detail page including the tree gets
> reloaded, even though the 's 'renderedPartially' value is set to
> body of the page(showing the detailed node info). This issue was raised and
> resolved during mid of '07(fixed in Tobago 1.0.12). This tree holds around
> 300 nodes (user Objects with 4-5 string properties). I have tried without
> mode="menu" as suggested by Helmut. Still the problem exists. I don't know,
> where and what I'm missing and I have been trying to fix this since two
> days...
>
> Here's the code, that I'm trying:
>
> nameReference="userObject.label" idReference="userObject.id"
> tipReference="userObject.label" state="#{mainTree.state}"
> showIcons="false" showJunctions="true" showRoot="false">
>
>
>
> name="renderedPartially" />
>
>
>
>
>
> Here's the portion of main page (where this detail page will have to be
> loaded)
>
>
>
> label="#{rsrcBundle.pageTitle}" id="mainpage" width="900px"
> height="830px">
>
> ..
>
>
>
>
> id="boxToolbarLayout" />
>
>
>
>
>
>
>
> columns="*;2*" />
>
>
> page="/WEB-INF/cdbmain/navigation.jsp" />
> <%--
>
>
>
>
> --%>
>
>
>
>
>
>
>
>
>
>
>
>
>
> .
>
> And in the generated html source, I could see the following:
>
> var mainpage_navigator_nav_treeNodeCommand = \"Tobago.reloadComponent
> ('mainpage:rightPanel',this.id, {});
>
>
> Appreciate your help!
> --
> Thanks,
>
> Raj .G. Narasimhan
>
>
--
Thanks,
Raj .G. Narasimhan
Re: [Tobago] renderedPartially doesn't work in treeNodeCommand
Hi,
actions called by ajax (renderedPartially) must not return an outcome (except
you really want to
navigate to another page).
Helmut
- Original Message -
From: Raj .G. Narasimhan
To: MyFaces Discussion
Sent: Wednesday, February 13, 2008 4:56 PM
Subject: Re: [Tobago] renderedPartially doesn't work in treeNodeCommand
Helmut, it does return "customer/custTabpane", which is the valid outcome to
be returnedand in fact, it loads the detail page also. Only issue, is the
tree is getting reloaded, (Moreover, this issue is more pronounce because the
tree's taking atleast 5-6 seconds to re-load ). The detail page loads pretty
quickly...compares to tree(and there's no need for the load to be reloaded)
thanks,
Raj
On Feb 13, 2008 10:40 AM, Helmut Swaczinna <[EMAIL PROTECTED]> wrote:
Hi,
just one idea: Does the action mainTree.showInDetail returns an outcome !=
null ?
If so the whole page gets reloaded.
Helmut
- Original Message -
From: Raj .G. Narasimhan
To: users@myfaces.apache.org
Sent: Wednesday, February 13, 2008 4:30 PM
Subject: [Tobago] renderedPartially doesn't work in treeNodeCommand
I'm having problem with partial reloading while invoking
'treeNodeCommand'. I am using Tobago 1.0.14 on Tomcat 6.
On clicking the node link, the detail page including the tree gets
reloaded, even though the 's 'renderedPartially' value is set to
body of the page(showing the detailed node info). This issue was raised and
resolved during mid of '07(fixed in Tobago 1.0.12). This tree holds around 300
nodes (user Objects with 4-5 string properties). I have tried without
mode="menu" as suggested by Helmut. Still the problem exists. I don't know,
where and what I'm missing and I have been trying to fix this since two days...
Here's the code, that I'm trying:
Here's the portion of main page (where this detail page will have to be
loaded)
..
<%--
--%>
.
And in the generated html source, I could see the following:
var mainpage_navigator_nav_treeNodeCommand =
\"Tobago.reloadComponent('mainpage:rightPanel',this.id, {});
Appreciate your help!
--
Thanks,
Raj .G. Narasimhan
--
Thanks,
Raj .G. Narasimhan
RE: [TRINIDAD] Dialog Framework behaving strange since Trinidad 1.2.3
Harald (anyone) - did you work out what's happening here? I think I'm hitting something similar. We've been successfully using 1.2.2 for a few months, but wanted to move up to 1.2.5 in order to consume a couple of bug fixes that we need. However, a number of our Selenium UI tests failed because of clicks on command links not responding after dialogs had been displayed. I've spent a bit of time trying to work out what's happening (not very successfully). The only observations I have made are: - The problem is intermittent but it only seems to occur after a lightweight dialog has been launched and closed *and*if the closure of the dialog results in a PPR refresh to a component on the underlying page - With firebug I can observe a javascript error occurring when the problem reproduces: _callChained is not defined DebugCommon1_2_5.js line 8408. Also, firebug seems to indicate that there is a POST to the server which has no response (though admittedly I'm not sure whether this is correct or relevant?) - I have tested Firefox and IE - it only seems to reproduce in Firefox - I've tested 1.2.3 up to 1.2.5 and the problem reproduces in all these versions (other issues are currently preventing testing of 1.2.6). Hence, it does seem like something that was introduced in 1.2.3. Any clues anyone? > Date: Sat, 15 Dec 2007 18:02:25 +0100 > From: [EMAIL PROTECTED] > To: users@myfaces.apache.org > Subject: Re: [TRINIDAD] Dialog Framework behaving strange since Trinidad 1.2.3 > > Ok, I tried the newest version of Tomcat (6.0.14) which reduced the > number of ClientAbortExceptions, although they still occur. > The problem still persists that after closing a dialog, the link for > opening it up again is not clickable for about 10 seconds (meaning > nothing happens when you click on it). > > Oh, and for Opera, dialogs won't work at all. After clicking on a link > that should launch a dialog, Opera seems to hang in a loop, reloading > the base page over and over again. > > So, anyone here who can provide me with some help? A developer who can > tell me what changes have been made to the dialog framework between > 1.2.2 and 1.2.3? > Also, should I file this as a bug? > > Harald. > > Harald Stangl schrieb: > > Hello, > > > > we're developing a browser game using JSF 1.2_04 (Sun RI) and Trinidad. > > > > Until now we are using Trinidad 1.2.2 where the lightweight dialogs > > work fine for both Internet Explorer and Firefox. > > > > But when we switched to Trinidad 1.2.4, the lightweight dialogs no > > longer worked reliably in Firefox. When clicking on a link that should > > launch a dialog often nothing happens at all, and sometimes the > > following Exception is thrown: > > ClientAbortException: java.net.SocketException: Software caused > > connection abort: socket write error > > > > When trying to spot the error, I made a peculiar observation: > > I included a Phase Listener for the RestoreViewPhase (although the > > phase is irrelevant in this case) that does nothing but gives me the > > possibility to set a break point. With Trinidad 1.2.2, the phase > > listener is called twice sequentially from the same thread upon the > > call of the dialog. I assume the first call is for the processing of > > the base page and the second one for the dialog page. > > > > But starting with Trinidad 1.2.3, the phase listener is called *four* > > times, where the two first calls occur sequentially as before, and the > > third and forth call happen in two different threads in parallel. This > > behaviour is special to Firefox; opening the dialog with Internet > > Explorer, only two sequential calls as with Trinidad 1.2.2 are being > > executed. > > > > I created a very simple test setup consisting of only two nearly empty > > pages (the base page and the dialog page), and a backing bean that > > handles the closing of the dialog when the "close" link in the dialog > > page is clicked. I also disabled any other filters or listeners to > > eliminate potential error sources. If there is any interest, I will be > > glad to post my demo files. Any help to solve this problem is > > appreciated. > > > > Thanks, > > Harald. > > > _ Free games, great prizes - get gaming at Gamesbox. http://www.searchgamesbox.com
Re: [Tobago] renderedPartially doesn't work in treeNodeCommand
Oh...ok... Actually, I was doing doBody defined in my main tag and trying to
expand it in another pageNow, I rewrote the code, and made the body
inline on the same page.It worked..!
THANKS A Trillion Helmut, for that tech tip!!!
-R
On Feb 13, 2008 11:10 AM, Helmut Swaczinna <[EMAIL PROTECTED]> wrote:
> Hi,
>
> actions called by ajax (renderedPartially) must not return an outcome
> (except you really want to
> navigate to another page).
>
> Helmut
>
>
>
> - Original Message -
> *From:* Raj .G. Narasimhan <[EMAIL PROTECTED]>
> *To:* MyFaces Discussion
> *Sent:* Wednesday, February 13, 2008 4:56 PM
> *Subject:* Re: [Tobago] renderedPartially doesn't work in treeNodeCommand
>
> Helmut, it does return "customer/custTabpane", which is the valid outcome
> to be returnedand in fact, it loads the detail page also. Only issue,
> is the tree is getting reloaded, (Moreover, this issue is more pronounce
> because the tree's taking atleast 5-6 seconds to re-load ). The detail page
> loads pretty quickly...compares to tree(and there's no need for the load to
> be reloaded)
>
>
> thanks,
> Raj
>
>
> On Feb 13, 2008 10:40 AM, Helmut Swaczinna <[EMAIL PROTECTED]>
> wrote:
>
> > Hi,
> >
> > just one idea: Does the action mainTree.showInDetail returns an outcome
> > != null ?
> > If so the whole page gets reloaded.
> >
> > Helmut
> >
> >
> > - Original Message -
> > *From:* Raj .G. Narasimhan <[EMAIL PROTECTED]>
> > *To:* users@myfaces.apache.org
> > *Sent:* Wednesday, February 13, 2008 4:30 PM
> > *Subject:* [Tobago] renderedPartially doesn't work in treeNodeCommand
> >
> > I'm having problem with partial reloading while invoking
> > 'treeNodeCommand'. I am using Tobago 1.0.14 on Tomcat 6.
> >
> > On clicking the node link, the detail page including the tree gets
> > reloaded, even though the 's 'renderedPartially' value is set to
> > body of the page(showing the detailed node info). This issue was raised and
> > resolved during mid of '07(fixed in Tobago 1.0.12). This tree holds
> > around 300 nodes (user Objects with 4-5 string properties). I have tried
> > without mode="menu" as suggested by Helmut. Still the problem exists. I
> > don't know, where and what I'm missing and I have been trying to fix this
> > since two days...
> >
> > Here's the code, that I'm trying:
> >
> > > nameReference="userObject.label" idReference="userObject.id"
> > tipReference="userObject.label" state="#{mainTree.state}"
> > showIcons="false" showJunctions="true" showRoot="false">
> >
> >
> >
> > > name="renderedPartially" />
> >
> >
> >
> >
> >
> > Here's the portion of main page (where this detail page will have to be
> > loaded)
> >
> >
> >
> > > label="#{rsrcBundle.pageTitle}" id="mainpage" width="900px"
> > height="830px">
> >
> > ..
> >
> >
> >
> >
> > > id="boxToolbarLayout" />
> >
> >
> >
> >
> >
> >
> >
> > > columns="*;2*" />
> >
> >
> > > page="/WEB-INF/cdbmain/navigation.jsp" />
> > <%--
> >
> > > />
> >
> >
> > --%>
> >
> >
> >
> >
> >
> > > />
> >
> >
> >
> >
> >
> >
> >
> > .
> >
> > And in the generated html source, I could see the following:
> >
> > var mainpage_navigator_nav_treeNodeCommand = \"Tobago.reloadComponent
> > ('mainpage:rightPanel',this.id, {});
> >
> >
> > Appreciate your help!
> > --
> > Thanks,
> >
> > Raj .G. Narasimhan
> >
> >
>
>
> --
> Thanks,
>
> Raj .G. Narasimhan
>
>
--
Thanks,
Raj .G. Narasimhan
Re: [Tobago] Problem migrating to 1.0.15
Hi there, I've tested it and I didn't found any problems. Can you build a simple standalone JSP of your problem? You may also check, if you've set the columns attribute of the sheet correctly. Regards, Udo yazid schrieb: Hi All; I've migrated last week to 1.0.15; most of component are OK, except for " Is that a bug in 1.0.15 or should I do a special use of select... Thanks
Re: [Tobago] Problem migrating to 1.0.15
Still not work, please Help I've tried the h:selectOneMenu.but I prefer tc:selectOneChoice ...better for facet. yazid wrote: > > Hi All; > I've migrated last week to 1.0.15; most of component are OK, except for > " > > > > > Is that a bug in 1.0.15 or should I do a special use of select... > Thanks > > > -- View this message in context: http://www.nabble.com/-Tobago--Problem-migrating-to-1.0.15-tp15438772p15462285.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Problem Solved: Re: [Trinidad] Tags aren't getting rendered (but I can see them when I go to view-source)
Problem Resolved: I found through more investigation that the problem stemmed from precompiling the JSP files in the application. After finding out that the application worked correctly when the jsp page precompilation was turned off, I looked at the ant task that I was using to precompile the jsp files. The problem was with the ojspc compiler and the need to have the .tld files for Trinidad and MyFaces or any tag library that are being used in the .jsp files being available externally. Once I extracted the .tld files for MyFaces and Trinidad from the myfaces-impl-1.1.5.jar and trinidad-impl-1.0.5.jar and made them available to the ant task, the application worked as expected and the tags were rendered correctly. -Richard On 2/10/08, Richard Yee <[EMAIL PROTECTED]> wrote: > > Thanks. I'm looking into that now. > > -R > > On Feb 7, 2008 10:34 PM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > On Feb 8, 2008 6:35 AM, Richard Yee <[EMAIL PROTECTED]> wrote: > > > Here's an update on my issue. It seems that if I build the project > > with Ant > > > in JDeveloper the .ear file can be deployed correctly. If the project > > is > > > built with Ant from the command line, I experience the problem that > > all tags > > > (MyFaces and Trinidad) aren't processed and can be seen in the > > View-Source > > > output. I have verified that I am using the same version of Ant to > > build. I > > > have looked at the exploded contents of the .ear and .war files and > > find > > > that they are mostly identical including the deployment descriptor > > files and > > > the libraries. There are a few differences in some of the files > > (different > > > dates in the manifest) but no obvious problems. > > > > > > that sounds like an error in the script that you wrote > > > > > > > > -Richard > > > > > > > > > > > > On Feb 7, 2008 1:25 PM, Rafa Pérez <[EMAIL PROTECTED]> wrote: > > > > Hi, I had similar problems after changing some configuration on > > web.xml. > > > Take a second look at it. You may clean the work directory on tomcat > > (or > > > cache directory elsewere) and stop server too. > > > > > > > > Regards, > > > > > > > > - - Rafa > > > > > > > > > > > > > > > > > > > > > > > > On Feb 7, 2008 3:25 PM, Matthias Wessendorf <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > hey > > > > > > > > > > please provide a simple WAR file, that runs in tomcat. > > > > > > > > > > -Matthias > > > > > > > > > > > > > > > > > > > > > > > > > On Feb 7, 2008 3:11 PM, Richard Yee <[EMAIL PROTECTED]> > > wrote: > > > > > > Matthias, > > > > > > My jar files are all under WEB-INF/lib. I really don't have any > > > enterprise > > > > > > components in my application. Do I need to put the myfaces and > > > trinidad > > > > > > libraries separately in the EAR file too? > > > > > > > > > > > > I can try that. The odd thing is that it has worked before and I > > > haven't > > > > > > changed the faces-config.xml and web.xml except for changing > > some of > > > the > > > > > > Trinidad context-params from their development settings. > > > > > > > > > > > > -R > > > > > > > > > > > > > > > > > > > > > > > > On Feb 6, 2008 11:22 PM, Matthias Wessendorf <[EMAIL PROTECTED]> > > > wrote: > > > > > > > Hi Richard > > > > > > > > > > > > > > > > > > > > > On Feb 7, 2008 6:15 AM, Richard Yee <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > I am using Trinidad 1.0.5 and MyFaces 1.1.5 with JDeveloper > > > 10.1.3.1. > > > > > > > > My application works fine in the embedded server but when I > > deploy > > > the > > > > > > ear > > > > > > > > file to the oc4j external container, my pages end up blank - > > The > > > browser > > > > > > > > window is empty and if I view the source, I can see all of > > the > > > > > > > > > tags. > > > > > > > > I have seen this problem before if the default-render-kit-id > > > element is > > > > > > not > > > > > > > > defined for trinidad (org.apache.myfaces.trinidad.core) . > > Does > > > anyone > > > > > > know > > > > > > > > what else > > > > > > > > might cause this problem? > > > > > > > > > > > > > > does your EAR contain all the required JARs ? > > > > > > > In embedded mode that may be different, since the embedded > > server > > > has the > > > > > > JARs > > > > > > > from your project. Not sure if your EAR contains them all as > > well. > > > > > > > > > > > > > > -M > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > Richard > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Matthias Wessendorf > > > > > > > > > > > > > > further stuff: > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > > > sessions: http://www.slideshare.net/mwessendorf > > > > > > > mail: matzew-at-apache-dot-org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > Matthias Wessendorf > > > > > > > > > > further st
[Tobago] Intercepting TreeExpansion event
Hi: I am wondering, is there any way to intercept TreeExpansion event, in Tobago API. My requirement is like this. As the tree, in my case, has around 500 nodes, and each node has three levels of children, it takes more than 30sec to load. So, I am thinking to add children nodes, whenever during tree expansion event (some TreeExpansionListnener-like implementation). Appreciate, any ideas, in this regard -- Thanks, Raj .G. Narasimhan
[Trinidad] tr:inputText read-only behaviour
Hi folks, I'm trying to show a tr:inputText with a (initial) value calculated from an EL expression (no value binding since the value will be read from the request), something like . But the input becomes "read-only". I found in the tag documentation and I think it is related: the value of the component. If the EL binding for the "value" points to a > bean property with a getter but no setter, and this is an editable > component, the component will be rendered in read-only mode. > Is there a way to make the inputText writable when it gets its value from an EL expression ? Thanks in advance, -- Walter Mourão http://waltermourao.com.br http://waltermourao.blogspot.com http://arcadian.com.br
[Trinidad] tr:inputText read-only behaviour
Hi folks, I'm trying to show a tr:inputText with a initial value from an EL expression (no value binding since the value will be read from the request). But the input becomes "read-only". I found in the tag documentation and I think it is related: the value of the component. If the EL binding for the "value" points to a > bean property with a getter but no setter, and this is an editable > component, the component will be rendered in read-only mode. > Is there a way to make the inputText writable when it gets its value from an EL expression ? Thanks in advance, -- Walter Mourão http://waltermourao.com.br http://waltermourao.blogspot.com http://arcadian.com.br
[OFFTOPIC] Reminder: JSFDays Vienna
Hi all, we'd like to invite you to a JSF conference in Vienna, Austria from 12-14th of March. Anyone who wants to register as an attendee? Here is the link: http://conference.irian.at - click on preregister. Attendees will pay a very small conference fee - 100€. Speaker slots are pretty much filled already - except you have a topic which just rocks ;) There will be a supporting programm alongside the conference - so you will (additionally to learning about JSF and improving your JSF knowledge) have a good chance of getting to know Vienna and its surroundings. So far, there have been close to a hundred registrations - so this conference is definitely going to be a meeting point for everyone interested in JSF! regards, Martin
[trinidad] Change how labels are calculated and displayed in a bar chart.
Hi, I'm currently using the Trinidad Chart component to display some statistics. My problem is that one of my display values is extremely large compared to the others. This cause the others bars to be drawn really small and the end users are complaining about that. What I want to know if it's possible to do is: Change the way the labels are calculated to have them in a logarithmic way. For example if I have 4 values, lets say: 3, 10, 20, 2100. I'd like to have the X-axis labels maybe as 10, 100, 1000, 1 (or something like this) instead of having the max value (2100) divided by 4 to have the size (and value) of each label. Thanks in advance, Jorge -- View this message in context: http://www.nabble.com/-trinidad--Change-how-labels-are-calculated-and-displayed-in-a-bar-chart.-tp15473909p15473909.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [Trinidad] tr:inputText read-only behaviour
Hi,
On Wed, Feb 13, 2008 at 6:02 PM, Walter Mourão <[EMAIL PROTECTED]> wrote:
> Hi folks,
> I'm trying to show a tr:inputText with a (initial) value calculated from an
> EL expression (no value binding since the value will be read from the
> request), something like . But
> the input becomes "read-only". I found in the tag documentation and I think
> it is related:
>
> > the value of the component. If the EL binding for the "value" points to a
> bean property with a getter but no setter, and this is an editable
> component, the component will be rendered in read-only mode.
> >
>
> Is there a way to make the inputText writable when it gets its value from an
> EL expression ?
this: #{bean.blah}
where there is a set/getBlah() in the "bean", the EL is not! readOnly.
if there is only a getBlah(), the EL is read-only.
A way around could be using , since there is no such an
additional read-only check.
-M
>
> Thanks in advance,
>
> --
> Walter Mourão
> http://waltermourao.com.br
> http://waltermourao.blogspot.com
> http://arcadian.com.br
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: [Trinidad] tr:inputText read-only behaviour
Walter Mourão schrieb:
> Hi folks,
> I'm trying to show a tr:inputText with a (initial) value calculated
> from an EL expression (no value binding since the value will be read
> from the request), something like value="#{fn:join(somevar)}" />. But the input becomes "read-only". I
> found in the tag documentation and I think it is related:
>
> the value of the component. If the EL binding for the "value"
> points to a bean property with a getter but no setter, and this is
> an editable component, the component will be rendered in read-only
> mode.
>
>
> Is there a way to make the inputText writable when it gets its value
> from an EL expression ?
If the component is editable, but there is no setter for the component
to store its new value into during postback, then what should it do?
In your example, there is no way that any data entered by the used can
be written back to "fn:join(somevar)", so any user data entered would
have to be thrown away on postback. Therefore when there is no setter
method, the *only* sane thing to do is make the component non-editable
or disabled.
Maybe what you are asking is for the component to be *disabled* rather
than *read-only*? That would seem to be reasonable..but how can a
"writable" field possibly be useful here?
Regards, Simon
