MasterDetail datatable, toggle all rows expanded, save state, detailStamp
Hello,
I am pretty new to JSF and MyFaces. I managed to use the master-detail
feature of the extended data table, and it works fine, except for 2
things :
First, Is it possible to set the initial state of the table to all rows
expanded (currentDetailExpanded=true) ?
I found related threads e.g. here
http://www.mail-archive.com/users@myfaces.apache.org/msg31418.html and
here http://www.mail-archive.com/users@myfaces.apache.org/msg31509.html
but no real answer. Anybody can help with that ?
Secondly, is it possible to store the state of the table so that when I
go to another page (e.g. edition of one of the entities managed in the
table or a new one) and then go back to the table, the rows that were
expanded still are expanded ? (something similar to the technique used
for storing the state of the scrolling here maybe :
http://wiki.apache.org/myfaces/ManagingDataScrollerPage?highlight=%28dat
ascroller%29)
I am working with MyFaces 1.1.4 and Tomahawk 1.1.5 snapshot.
And finally here is my code for the table :
t:dataTable
headerClass=standardTable_Header
footerClass=standardTable_Header
rowClasses=standardTable_Row2
styleClass=standardTable
id=domainsDataTable
width=800px
align=left
border=0
cellspacing=2
cellpadding=2
var=domain
rows=10
preserveDataModel=true
rendered=true
value=#{domainsList.domains}
varDetailToggler=domainsDetailToggler
t:column width=20px
h:commandButton
rendered=#{domainsDetailToggler.currentDetailExpanded}
action=#{domainsDetailToggler.toggleDetail}
image=images/tree-collapse.gif
/h:commandButton
h:commandButton
rendered=#{!domainsDetailToggler.currentDetailExpanded}
action=#{domainsDetailToggler.toggleDetail}
image=images/tree-expand.gif
/h:commandButton
/t:column
t:column width=700px
f:facet name=header
h:outputText
value=#{bundle.domain_name}
style=width:30% /
/f:facet
h:commandLink
immediate=true
action=go_domainForm
rendered=true
value=#{domain.name}
t:updateActionListener
property=#{domainForm.domainId}
value=#{domain.domainId} /
/h:commandLink
/t:column
t:column width=120px
f:facet name=header
h:outputText
value=#{bundle.lists_action} /
/f:facet
h:panelGrid columns=5
h:commandButton
immediate=true
action=#{domainForm.moveUp}
rendered=true
value=#{bundle.lists_action_edit}
title=#{bundle.lists_action_edit}
image=images/icons/arrow-up.gif
t:updateActionListener
property=#{domainForm.domainId}
value=#{domain.domainId} /
/h:commandButton
Some other buttons here...
/h:panelGrid
/t:column
f:facet name=detailStamp
Here comes a t:dataTable really similar to the main Data
table.
/f:facet
f:facet name=footer
/f:facet
/t:dataTable
Thanks in advance for any hint,
Pierre Henry
Tobago Not working in JDev(OC4J)
Hello everybody, I'm new to my faces. I'm trying to use trinidad ,tomahawk and tobago together in the same application. But first things first. I'm able to work with trinidad, and tomahawk individually;but I'm getting problem with integrating them getting the error : No RenderingContext And then I tried my luck with tobago ,with out any other libraries. Some of the components,like label,out,textArea , are working but most of the the components are giving me error : javax.servlet.ServletException: InValid to flush BodyContent: no backing stream behind it I'm JDeveloper with Embedded OC4J running in it. Can you please help me fix the issue? Thanking you in advance, Samba. -- Regards... Samba.
Re: jscookmenu
I'am using JSCookMenu of Tomahawk 1.1.3 in a Studio Creator 2.1 project with Sun RI 1.1_01. I have to add input type=hidden name=jscook_action / to JSP too. Another bug is maybe in the Renderer. When I use both action methods and action listeners in the same menu and click on a action link, the action listeners from the previous request were called. Maybe this is influenced by the fact, that the menu is part of a page fragment. My workaround is - not to use action methods - always set the action attribute to a non null value - always set the value unequal to null I don't know if this is a known feature. If you are interested in a test case I would create a minimal project. It's some work because I'am using a database in the project (the menu is dynamically created dependent on the permissions of the user) and must create a new project. That's why I can complete this still in a few days and you have to wait. Paul Spencer schrieb: Pierre, I am not sure I understand you answer. Are you saying the HTML generated by t:jscookMenu is missing input type=hidden name=jscook_action /? Can you open an issue and submit a patch. Paul Spencer Pierre Raoul wrote: Paul, I asked a similar question [1]. I suspect their is a bug because the action is not called when the menu item is clicked. I do not think you want the action called when the menu item is generated, which would occur when the EL is evaluated. Thank you for your reply. I found the answer: a tag input type=hidden name=jscook_action / is needed before the jscookmenu one. I still have some issues with the menu styles, but it works. Pierre
wat is the main advantage of aliasbean component
Hi All, I'm new to MyFaces components. I could not understand how can we make use of t:aliasbean component. When there is a managed bean, why to go for t:aliasbean. Where can i find the effective use of t:aliasbean. I mean in which situation we can go for t:aliasbean component. Thanks in advance, regards, satish -- View this message in context: http://www.nabble.com/wat-is-the-main-advantage-of-aliasbean-component-tf3147876.html#a8726466 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: s:inputSuggestAjax - encoding Problem
Hi, i know this encoding issue (think there is a corresponding jira issue too), but still had no time to work on it. Maybe i can invest some time during next week, but i can not give a guarantee on it. cheers, Gerald On 1/29/07, Birgit Kaschte [EMAIL PROTECTED] wrote: Hi, I've got a problem with s:inputSuggestAjax and the encoding of German 'Umlaute'. I tried using t:dojoInitializer bindEncoding=utf-8/ which had no effect. I also tried setting the parameter 'charset' of s:inputSuggestAjax to 'utf-8'. This had the effect that the items in the list were displayed correctly but the selected item was not. I would be glad for any suggestions on how to solve this problems. Cheers, Birgit -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: modalDialog scrolls endlessly on page
Hi,
the modalDialog component uses the dojo js-lib dialog widget. Any js
related problems can not be solved by myfaces developers, they are
only dojo-related. Maybe you can find help with this issue on the dojo
list.
Apart from this, it maybe an issue you can live with; i also use the
modalDialog in an application and it works very well.
The current sandbox snapshot with the dialog component is deployed here:
http://example.irian.at/example-sandbox-20070131/dojo/dojoDialog.jsf
If you click on searchOuterForm, the dialog accomplishes the same
usecase as you have with the form. Seems to work there.Have a look at
the source of the example, maybe it can assist.
What you mean by unable to enter? Are the input fields hidden, or
disabled? Does the post not happen?
cheers,
Gerald
On 1/31/07, Joshua Pheneger [EMAIL PROTECTED] wrote:
My company is evaluating myFaces as the UI framework for a large upcoming
project and I am having a couple of issues:
1. When I display a modalDialog, I am able to scroll the page down
endlessly. The dialog repositions itself, but portions of it are outside of
the viewable space on the page. It seems that the getScrolling javascript
function that gets added to the page upon rendering does not account for
reaching the bottom of the page.
h:outputLink value=#
onclick=dojoDialog.show();document.getElementById('higherId').focus();
h:outputText value=Scroll View /
/h:outputLink
aTab View/a
/div
b:modalDialog dialogId=DialogContent dialogVar=dojoDialog
dialogAttr=bgColor='white' bgOpacity='0.5' toggle='fade'
toggleDuration='250'
hiderIds=cancel1 styleClass=dojoDialog
!-- // Main Content --
h:panelGrid columns=1 id=hiderId
b:commandButton id=cancel1 forceId=true value=Cancel
onclick=dojo.widget.byId('DialogContent').hide(); /
2. When creating a dialog that will act as a form, I am unable to enter text
into the input field.
b:modalDialog dialogId=TripDatesDialogContent
dialogVar=tripDatesDialog
dialogAttr=bgColor='white' bgOpacity='0.5' toggle='fade'
toggleDuration='250'
hiderIds=cancel2 styleClass=dojoDialog
h:panelGrid
input type=text name=something value=myvalue id=newdates
size=25/
b:commandButton id=cancel2 forceId=true value=Cancel
onclick=dojo.widget.byId('TripDatesDialogContent').hide();
/
/h:panelGrid
Any assistance you can provide will be greatly appreciated and will be taken
into account when evaluating your product.
Regards,
Joshua Pheneger
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: wat is the main advantage of aliasbean component
Hi,
the main advantage when using t:aliasBean it reusing existing pages.
Consider having a fragment page, which you want to use in other pages. This
page fragment doesn`t access components like a dataTable per
#{managedBean.list}, it
does its job the way like #{list}.
E.g.:
t:dataTable value=#{list} ..
/t:dataTable
So, in the pages where you want to use the fragment, you can write:
t:aliasBean alias=#{list} value=#{firstManagedBean.list}
jsp:include page=pageFragment.jsp/
/t:aliasBean
The next page:
t:aliasBean alias=#{list} value=#{secondManagedBean.list}
jsp:include page=pageFragment.jsp/
/t:aliasBean
It is a generic way of including pages by using a so called alias.
Coherent now?
cheers,
Gerald
On 1/31/07, dasara [EMAIL PROTECTED] wrote:
Hi All,
I'm new to MyFaces components. I could not understand how can we make use of
t:aliasbean component.
When there is a managed bean, why to go for t:aliasbean.
Where can i find the effective use of t:aliasbean. I mean in which
situation we can go for t:aliasbean component.
Thanks in advance,
regards,
satish
--
View this message in context:
http://www.nabble.com/wat-is-the-main-advantage-of-aliasbean-component-tf3147876.html#a8726466
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: Dojo widgets not working on IE
Catalin Kormos schrieb: Hi, I just tryied the sandbox examples app, after a fresh update from the SVN. The dojo based components don't work there neither, in IE. Is this a known issue? any ideea would be greatly appreciated. Hi Catalin, not really a known issue... since when has it been broken for you?
RE: Problem by opening a page in new browser
Hello Thomas, I ran into the same problem earlier. I creates an issue for this in JIRA (https://issues.apache.org/jira/browse/MYFACES-1526) Pending it's resolution I change my application, so that it doesn't need the popups any more. With kind regards, Marco From: Thomas Chang [mailto:[EMAIL PROTECTED] Sent: dinsdag 30 januari 2007 16:08 To: MyFaces Discussion Subject: Problem by opening a page in new browser Hi all, The following is my code. What I wan tto do is: If I click the link, it will open a page in a new browser. It does. But my problem is: after I close the new opened browser, the first page dosen't work. It seems it is waitting for somewhat. What's wrong? Thanks Thomas myFirstPage.xHtml ... t:commandLink id=newBrowser value=Open New Browser action=openNewBrowser target=_blank immediate=true /t:commandLink ... faces-config.xml * ... navigation-rule descriptionOpen a new browser to show the result of Eingabedatenerfassen/description navigation-case from-outcomeopenNewBrowser/from-outcome to-view-id/newPage.xhtml/to-view-id /navigation-case /navigation-rule ... Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail http://de.rd.yahoo.com/evt=40589/*http://de.docs.yahoo.com/ymail/landing.html . -- Notice: This e-mail message, together with any attachments, contains information of Merck Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. --
Re: Dojo widgets not working on IE
Hi Catalin, are you sure that this is not a local problem? I have tried the latest Irian examples on IE, and the dojo corresponding stuff worked fine to me. And I don`t think that this is facelets related. (because examples are in jsp) cheers, Gerald On 1/29/07, Catalin Kormos [EMAIL PROTECTED] wrote: Hi, Any of you experiencing problems using Dojo based components on IE, like modalDialog or inputSuggestAjax? i keep getting this kind of messages, and only on IE: Jan 29, 2007 9:48:13 PM org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource SEVERE: Unable to find resource src/widget.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory. It works perfectly fine on Firefox, and it did worked on IE too, a few days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN with facelets. Thanks, Catalin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: stateChangeNotifier does not work with t:commandButton properly
Some months ago...
http://comments.gmane.org/gmane.comp.jakarta.myfaces.user/26829
Any changes?
On 1/29/07, Madhav Bhargava [EMAIL PROTECTED] wrote:
I just looked at the renderer code for this component:
In the encodeJavascript method following line is present:
sb.append(*setTimeout('* + replacedClientId +
*Notifier.prepareNotifier()',500);\n*);
This will add a timeout of 500. However this setting does not have any
effect on command links. Moreover should not this value be configurable? If
someone does not want a timeout, rather wants to use to necessary choose
before moving ahead then he/she will not be able to do it.
~madhav
--
*From:* Madhav Bhargava [mailto:[EMAIL PROTECTED]
*Sent:* Monday, January 29, 2007 1:12 PM
*To:* MyFaces Discussion
*Subject:* stateChangeNotifier does not work with t:commandButton properly
Hi All,
I have been looking for a component like s:stateChangeNotifier for quite
some time and I am glad that it is there is sandbox finally.
The problem with this component is that it does not work properly with
t:commandButton component.
Consider the following code:
s:stateChangedNotifier
confirmationMessage=There are changes in the form. You will
loose all data if you choose to leave the form. Do you want to cancel?
excludedIds=_patientRegistration_proceed,
_patientRegistration_reset disabled=false/
And then you have the following buttons:
t:commandButton id=_patientRegistration_proceed forceId=true
value=Proceed action=#{patientRegistrationWizardBean.proceed}
actionFor=patientRegistration/
t:commandButton id=_patientRegistration_reset forceId=true
value=#{msg['button.demographicdetails.reset']} action=#{
patientRegistrationWizardBean.reset}/
t:commandButton id=_patientRegistration_cancel forceId=true
value=Cancel action=#{patientRegistrationWizardBean.cancel}/
Now the problem is that when I click the Cancel button then the popup
only appears for 2 seconds and then it vanishes and the control goes to the
action method attached with the command button.
However, this problem is not there with the command link. I have something
like:
t:commandLink id=_patientRegistration_dummy forceId=true
value=dummy/
Now if I click this link then the modal popup stays there till you click a
link.
I have following questions:
1. Does this component only work with t:commandLink component?
2. If I have a datagrid and one of the columns in the datagrid is a link
View Details. Say if there are 20 rows displayed in one page and there are
other command buttons on the page to control navigation. Then will I have to
put all the ID's for all the links in the column to prevent the popup
appearing on click of any of the View Details link?
Rgds,
Madhav
CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
solely for the use of the addressee(s). If you are not the intended
recipient, please notify the sender by e-mail and delete the original
message. Further, you are not to copy, disclose, or distribute this e-mail
or its contents to any other person and any such actions are unlawful. This
e-mail may contain viruses. Infosys has taken every reasonable precaution to
minimize this risk, but is not liable for any damage you may sustain as a
result of any virus in this e-mail. You should carry out your own virus
checks before opening the e-mail or attachment. Infosys reserves the right
to monitor and review the content of all messages sent to or from this
e-mail address. Messages sent to or from this e-mail address may be stored
on the Infosys e-mail system.
***INFOSYS End of Disclaimer INFOSYS***
Re: wat is the main advantage of aliasbean component
Hi,
In addition, here's an example that might help;
http://www.jroller.com/page/cagataycivici?entry=jsf_composition_components_with_aliasbean
Regards,
Cagatay
On 1/31/07, Gerald Müllan [EMAIL PROTECTED] wrote:
Hi,
the main advantage when using t:aliasBean it reusing existing pages.
Consider having a fragment page, which you want to use in other pages.
This
page fragment doesn`t access components like a dataTable per
#{managedBean.list}, it
does its job the way like #{list}.
E.g.:
t:dataTable value=#{list} ..
/t:dataTable
So, in the pages where you want to use the fragment, you can write:
t:aliasBean alias=#{list} value=#{firstManagedBean.list}
jsp:include page=pageFragment.jsp/
/t:aliasBean
The next page:
t:aliasBean alias=#{list} value=#{secondManagedBean.list}
jsp:include page=pageFragment.jsp/
/t:aliasBean
It is a generic way of including pages by using a so called alias.
Coherent now?
cheers,
Gerald
On 1/31/07, dasara [EMAIL PROTECTED] wrote:
Hi All,
I'm new to MyFaces components. I could not understand how can we make
use of
t:aliasbean component.
When there is a managed bean, why to go for t:aliasbean.
Where can i find the effective use of t:aliasbean. I mean in which
situation we can go for t:aliasbean component.
Thanks in advance,
regards,
satish
--
View this message in context:
http://www.nabble.com/wat-is-the-main-advantage-of-aliasbean-component-tf3147876.html#a8726466
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: breadcrumb JSF component
Madhav Bhargava Madhav_Bhargava at infosys.com writes: I have a couple of questions: 1. How will you handle back button? 2. How will you stack navigation? In the web app that I am developing there are multiple ways in which you can come to a page. 3. Say if I have a breadcrumb shown on a particular page (Home Functionality 1 Functionality 2). Now I click a link on the left menu which takes me to a totally different functionality, so now the bread crumb should look like - (Home Functionality 3). How are you taking care of this? Dear Madhav, do you have some answers to all these interesting questions ? I need also to create a breadcrumb like you describe and to prepare a navigation stack manager... best regards Marc Amir-Tahmasseb
Re: Dojo widgets not working on IE
Gerald Müllan schrieb: Hi Catalin, are you sure that this is not a local problem? I have tried the latest Irian examples on IE, and the dojo corresponding stuff worked fine to me. And I don`t think that this is facelets related. (because examples are in jsp) cheers, Gerald I am aware of one single issue if you use xhmtl in conjunction with ie 6 and you have a simple base href=... / tag instead of base ../base the ie starts to choke, this is a known issue in dojo- But this is hardly the problem catalin faces.
AW: s:inputSuggestAjax - encoding Problem
Hi, thanks Gerald for the answer. It would be great if you can have a look at this problem. I found the jira issue (http://issues.apache.org/jira/browse/TOMAHAWK-748) which is set to 'fixed'. Can anyone confirm, that the problem still exists as described. If this is the case, someone should reopen the jira issue. Cheers, Birgit -Ursprüngliche Nachricht- Von: Gerald Müllan [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 31. Januar 2007 11:20 An: MyFaces Discussion Betreff: Re: s:inputSuggestAjax - encoding Problem Hi, i know this encoding issue (think there is a corresponding jira issue too), but still had no time to work on it. Maybe i can invest some time during next week, but i can not give a guarantee on it. cheers, Gerald On 1/29/07, Birgit Kaschte [EMAIL PROTECTED] wrote: Hi, I've got a problem with s:inputSuggestAjax and the encoding of German 'Umlaute'. I tried using t:dojoInitializer bindEncoding=utf-8/ which had no effect. I also tried setting the parameter 'charset' of s:inputSuggestAjax to 'utf-8'. This had the effect that the items in the list were displayed correctly but the selected item was not. I would be glad for any suggestions on how to solve this problems. Cheers, Birgit -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Dojo widgets not working on IE
Werner Punz schrieb: I am aware of one single issue if you use xhmtl in conjunction with ie 6 and you have a simple base href=... / tag instead of base ../base the ie starts to choke, this is a known issue in dojo- But this is hardly the problem catalin faces. Ok I rechecked the sandbox on a build I did yesterday. Dojo generally works, but the fisheye for me is broken (probably an error which I introduced yesterday night by fixing a few other issues) the ajax autocomplete also is broken, probably a timing issue because onload is used (this always is inherently evil), I or Gerald who programmed the control have to look into that. but all other controls utilizing dojo seem to work on me, so far. The table suggest, the ppr, the split pane etc... Catalin you can do a check here: http://wuerg.kicks-ass.net:8080/tomahawk-sandbox-examples/ this is my private machine running on a yesterday night build of the sandbox.
Re: Dojo widgets not working on IE
Catalin Kormos schrieb: Hi, Any of you experiencing problems using Dojo based components on IE, like modalDialog or inputSuggestAjax? i keep getting this kind of messages, and only on IE: Jan 29, 2007 9:48:13 PM org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource SEVERE: Unable to find resource src/widget.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory. It works perfectly fine on Firefox, and it did worked on IE too, a few days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN with facelets. Ah ok sorry for this confusion, there indeed is a bug but it is ie only. I tried the dialog as well and can reproduce the problem, it must have been introduced somewhere in the dojo utils, I am affected by it as well. I will look into it, not quite sure what it is probably an initialisation timing issue. Best bet to nail it down for now is to check the change history of the dojo utils if someone has introduced a fix into the component creation code which broke it. I have to look into that due to a similar problem in the fisheye someone reported me as well, so I will be onto it in about two hours. Werner
Re: Dojo widgets not working on IE
Catalin Kormos schrieb: Hi, Any of you experiencing problems using Dojo based components on IE, like modalDialog or inputSuggestAjax? i keep getting this kind of messages, and only on IE: Jan 29, 2007 9:48:13 PM org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource SEVERE: Unable to find resource src/widget.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory. It works perfectly fine on Firefox, and it did worked on IE too, a few days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN with facelets. Ok I filed a bugreport on this one, I will start to investigate into it tonight.
Re: modalDialog scrolls endlessly on page
Gerald Müllan schrieb: Hi, the modalDialog component uses the dojo js-lib dialog widget. Any js related problems can not be solved by myfaces developers, they are only dojo-related. Maybe you can find help with this issue on the dojo list. The dialog issue is an issue with the dojo dialog itself, there is a parameter in the dojo baselib which can prevent this behavior (it is called centerdialog or so, you really have to check the dialog sources for this) I rember having such a param at least in dojo 0.4.1 which is the latest currently being in tomahawk I am not sure if it already is exposed. There also is the possibility to use floating panes instead of the dialog. Apart from this, it maybe an issue you can live with; i also use the modalDialog in an application and it works very well. The current sandbox snapshot with the dialog component is deployed here: http://example.irian.at/example-sandbox-20070131/dojo/dojoDialog.jsf If you click on searchOuterForm, the dialog accomplishes the same usecase as you have with the form. Seems to work there.Have a look at the source of the example, maybe it can assist. What you mean by unable to enter? Are the input fields hidden, or disabled? Does the post not happen? The code looks to me as if the form is declared outside of the dialog this is not possible due to browser limitations, mainly caused by the broken ie css implementation. If you want to use the dialog in conjunction with forms use it outside of any form definition and put the form into the dialog, there are various ways to savestate the affected values, so that you do not have to push all page related values into the dialog. (for most cases a simple savestate on a bean should do it)
Re: Doesn't Oracle 10g application Server Support MyFaces 1.1.3 ???
As I mentioned on the facelets mailing list (where this issue was previously posted), the problem isn't commons-digester, it's with whatever parser that commons-digester is trying to use. If there were no digester in the path, you wouldn't be getting exceptions from Digester classes == Well, assuming this is commons-digester 1.3, reader = getParser().getXMLReader(); So the problem is that the digester hasn't been initialized with a parser. Not really sure what would cause that, but it's probably outside of the scope of facelets or JSF. == However, maybe the issue is a missing parser jar file. On 1/31/07, Mick Knutson [EMAIL PROTECTED] wrote: It sounds like Tomcat has commons-digester, but Oracle does not... org.apache.commons.digester.Digester.getXMLReader(Digester.java:891) Try including it in your war/ear On 1/30/07, bansi [EMAIL PROTECTED] wrote: I have a web application developed using Facelets 1.1.12, Ajax4Jsf 1.0.4 which works absolutely fine on Tomcat 5.5.17 but when i deploy the same web application onto Oracle 10g Application Server version 10.1.3 it throws Null Pointer Exception Here is the stack trace 07/01/30 14:52:31 log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader). 07/01/30 14:52:31 log4j:WARN Please initialize the log4j system properly. 07/01/30 14:52:34 java.lang.NullPointerException 07/01/30 14:52:34 at org.apache.commons.digester.Digester.getXMLReader(Digester.java:891) 07/01/30 14:52:34 at org.apache.commons.digester.Digester.parse (Digester.java:1572) 07/01/30 14:52:34 at org.apache.myfaces.config.impl.digester.DigesterFacesConfigUnmarshallerImpl.getF acesConfig(DigesterFacesConfigUnm arshallerImpl.java:183) 07/01/30 14:52:34 at 2007-01-30 16:43:40,680 ERROR [org.apache.myfaces.webapp.StartupServletContextListener] - Error initializing ServletContext java.lang.NullPointerException at org.apache.commons.digester.Digester.getXMLReader (Digester.java:891) at org.apache.commons.digester.Digester.parse(Digester.java:1572) at org.apache.myfaces.config.impl.digester.DigesterFacesConfigUnmarshallerImpl.getF acesConfig(DigesterFacesConfigUnmarshallerImpl.java :183) at org.apache.myfaces.config.FacesConfigurator.feedStandardConfig(FacesConfigurator .java:152) at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:126 ) at org.apache.myfaces.webapp.StartupServletContextListener.initFaces (StartupServlet ContextListener.java:69) -- View this message in context: http://www.nabble.com/Doesn%27t-Oracle-10g-application-Server-Support-MyFaces-1.1.3-tf3146181.html#a8721743 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- --- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/djmick_dot_com http://www.thumpradio.com ---
Re: stateChangeNotifier does not work with t:commandButton properly
Hi Nako,
Thanks for the pointer.
I have to use a command button.
Is there anyway (apart from styling the command link as a button) to check
if there is a change in the form when the user tries to go some where else?
Thanks,
Madhav
On 1/31/07, Nacho Estrada [EMAIL PROTECTED] wrote:
Some months ago...
http://comments.gmane.org/gmane.comp.jakarta.myfaces.user/26829
Any changes?
On 1/29/07, Madhav Bhargava [EMAIL PROTECTED] wrote:
I just looked at the renderer code for this component:
In the encodeJavascript method following line is present:
sb.append(*setTimeout('* + replacedClientId +
*Notifier.prepareNotifier()',500);\n*);
This will add a timeout of 500. However this setting does not have any
effect on command links. Moreover should not this value be configurable? If
someone does not want a timeout, rather wants to use to necessary choose
before moving ahead then he/she will not be able to do it.
~madhav
--
*From:* Madhav Bhargava [mailto:[EMAIL PROTECTED]
*Sent:* Monday, January 29, 2007 1:12 PM
*To:* MyFaces Discussion
*Subject:* stateChangeNotifier does not work with t:commandButton
properly
Hi All,
I have been looking for a component like s:stateChangeNotifier for quite
some time and I am glad that it is there is sandbox finally.
The problem with this component is that it does not work properly with
t:commandButton component.
Consider the following code:
s:stateChangedNotifier
confirmationMessage=There are changes in the form. You will
loose all data if you choose to leave the form. Do you want to cancel?
excludedIds=_patientRegistration_proceed,
_patientRegistration_reset disabled=false/
And then you have the following buttons:
t:commandButton id=_patientRegistration_proceed forceId=true
value=Proceed action=#{patientRegistrationWizardBean.proceed}
actionFor=patientRegistration/
t:commandButton id=_patientRegistration_reset forceId=true
value=#{msg['button.demographicdetails.reset']} action=#{
patientRegistrationWizardBean.reset}/
t:commandButton id=_patientRegistration_cancel forceId=true
value=Cancel action=#{patientRegistrationWizardBean.cancel}/
Now the problem is that when I click the Cancel button then the popup
only appears for 2 seconds and then it vanishes and the control goes to the
action method attached with the command button.
However, this problem is not there with the command link. I have
something like:
t:commandLink id=_patientRegistration_dummy forceId=true
value=dummy/
Now if I click this link then the modal popup stays there till you click
a link.
I have following questions:
1. Does this component only work with t:commandLink component?
2. If I have a datagrid and one of the columns in the datagrid is a link
View Details. Say if there are 20 rows displayed in one page and there are
other command buttons on the page to control navigation. Then will I have to
put all the ID's for all the links in the column to prevent the popup
appearing on click of any of the View Details link?
Rgds,
Madhav
CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
solely for the use of the addressee(s). If you are not the intended
recipient, please notify the sender by e-mail and delete the original
message. Further, you are not to copy, disclose, or distribute this e-mail
or its contents to any other person and any such actions are unlawful. This
e-mail may contain viruses. Infosys has taken every reasonable precaution to
minimize this risk, but is not liable for any damage you may sustain as a
result of any virus in this e-mail. You should carry out your own virus
checks before opening the e-mail or attachment. Infosys reserves the right
to monitor and review the content of all messages sent to or from this
e-mail address. Messages sent to or from this e-mail address may be stored
on the Infosys e-mail system.
***INFOSYS End of Disclaimer INFOSYS***
--
When I tell the truth, it is not for the sake of convincing those who do not
know it, but for the sake of defending those that do
RE: Re: modalDialog scrolls endlessly on page
I will file a bug with the dojo team to investigate the dialog scrolling issue.
Can you clarify your response on the form text field issue? Is it
possible/recommended to use a form within a dialog that is sitting on top of
another dialog? What would the code look like? The following code does not
allow the text field to be edited.
b:modalDialog dialogId=TripDatesDialogContent dialogVar=tripDatesDialog
dialogAttr=bgColor='white' bgOpacity='0.5' toggle='fade'
toggleDuration='250'
hiderIds=cancel2 styleClass=dojoDialog
h:form
h:panelGrid
input type=text name=something value=myvalue
id=newdates size=25/
b:commandButton id=cancel2 forceId=true
value=Cancel
onclick=dojo.widget.byId('TripDatesDialogContent').hide(); /
/h:panelGrid
/h:form
/b:modalDialog
Regards,
Joshua Pheneger
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz
Sent: Wednesday, January 31, 2007 8:22 AM
To: users@myfaces.apache.org
Subject: Re: modalDialog scrolls endlessly on page
Gerald Müllan schrieb:
Hi,
the modalDialog component uses the dojo js-lib dialog widget. Any js
related problems can not be solved by myfaces developers, they are
only dojo-related. Maybe you can find help with this issue on the dojo
list.
The dialog issue is an issue with the dojo dialog itself, there is a parameter
in the dojo baselib which can prevent this behavior (it is called centerdialog
or so, you really have to check the dialog sources for this) I rember having
such a param at least in dojo 0.4.1 which is the latest currently being in
tomahawk
I am not sure if it already is exposed.
There also is the possibility to use floating panes instead of the dialog.
Apart from this, it maybe an issue you can live with; i also use the
modalDialog in an application and it works very well.
The current sandbox snapshot with the dialog component is deployed here:
http://example.irian.at/example-sandbox-20070131/dojo/dojoDialog.jsf
If you click on searchOuterForm, the dialog accomplishes the same
usecase as you have with the form. Seems to work there.Have a look at
the source of the example, maybe it can assist.
What you mean by unable to enter? Are the input fields hidden, or
disabled? Does the post not happen?
The code looks to me as if the form is declared outside of the dialog this is
not possible due to browser limitations, mainly caused by the broken ie css
implementation.
If you want to use the dialog in conjunction with forms use it outside of any
form definition and put the form into the dialog, there are various ways to
savestate the affected values, so that you do not have to push all page related
values into the dialog.
(for most cases a simple savestate on a bean should do it)
Javscript Issues with JSF 1.2, Tomahawk 1.1.3
Using JSF 1.2 with Tomahawk 1.1.3 is causing issues with several of the components developed in our application. The dynamic menus and static menus developed using panelNavigation2 aren't working. There is javascript error detected. The javascript error is 'Object Expected'. So, I set to explore just a simple example of a commandLink. The below code has an error, I'm using the tomahawk's commandLink component. t:commandLink action=welcome f:verbatim#8250; /f:verbatim t:outputText value=Test Client / /t:commandLink Changing the t:commandLink to h:commandLink works. Is tomahawk 1.1.3 not compatible with JSF 1.2? Previously we were using myfaces-1.1.4 and it worked great. Also, another strange behavior with JSF 1.2 is that our xhtml files appear as raw files when being displayed in Mozilla browser, if I use IE 6 or IE 7 there isn't an issue. This wasn't the case with myfaces1.1.4. Thanks. -Bharath
Re: modalDialog scrolls endlessly on page
Ok I only see one problem
you mix and match html input fields
with jsf forms there ,
I am not sure how facelets behave
there, but you ask for trouble regarding other stuff (like automatic
value assigment, automatic validation etc...)
try to replace your simple input field with the jsf equivalent
h:inputText or t:inputText.
What should happen is, first, you should be able to edit the fields
secondly, you should be able to submit the form, and get the values into
the beans assigned to the field.
Check the tomahawk-sandbox-examples for exactly this usecase, like
gerald pointed it out.
As for stacking dialogs, yes it is possible, but i do not know how
it behaves formwise, but I assume following
first dialog has a form, second one is opened
after the first one, it should be stacked on top of the first one
also has a form, you submit the form in the second dialog
and trigger a page refresh, the values of the second form should be
assigned to the backend beans, and you will basically lose
both dialogs, the changed values of the first dialog will be lost however!.
Joshua Pheneger schrieb:
I will file a bug with the dojo team to investigate the dialog scrolling
issue.
Can you clarify your response on the form text field issue? Is it
possible/recommended to use a form within a dialog that is sitting on top of
another dialog? What would the code look like? The following code does not
allow the text field to be edited.
b:modalDialog dialogId=TripDatesDialogContent dialogVar=tripDatesDialog
dialogAttr=bgColor='white' bgOpacity='0.5' toggle='fade'
toggleDuration='250'
hiderIds=cancel2 styleClass=dojoDialog
h:form
h:panelGrid
input type=text name=something value=myvalue
id=newdates size=25/
b:commandButton id=cancel2 forceId=true
value=Cancel
onclick=dojo.widget.byId('TripDatesDialogContent').hide(); /
/h:panelGrid
/h:form
/b:modalDialog
Regards,
Joshua Pheneger
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz
Sent: Wednesday, January 31, 2007 8:22 AM
To: users@myfaces.apache.org
Subject: Re: modalDialog scrolls endlessly on page
Gerald Müllan schrieb:
Hi,
the modalDialog component uses the dojo js-lib dialog widget. Any js
related problems can not be solved by myfaces developers, they are
only dojo-related. Maybe you can find help with this issue on the dojo
list.
The dialog issue is an issue with the dojo dialog itself, there is a
parameter in the dojo baselib which can prevent this behavior (it is called
centerdialog or so, you really have to check the dialog sources for this) I
rember having such a param at least in dojo 0.4.1 which is the latest
currently being in tomahawk
I am not sure if it already is exposed.
There also is the possibility to use floating panes instead of the dialog.
Apart from this, it maybe an issue you can live with; i also use the
modalDialog in an application and it works very well.
The current sandbox snapshot with the dialog component is deployed here:
http://example.irian.at/example-sandbox-20070131/dojo/dojoDialog.jsf
If you click on searchOuterForm, the dialog accomplishes the same
usecase as you have with the form. Seems to work there.Have a look at
the source of the example, maybe it can assist.
What you mean by unable to enter? Are the input fields hidden, or
disabled? Does the post not happen?
The code looks to me as if the form is declared outside of the dialog this is
not possible due to browser limitations, mainly caused by the broken ie css
implementation.
If you want to use the dialog in conjunction with forms use it outside of any
form definition and put the form into the dialog, there are various ways to
savestate the affected values, so that you do not have to push all page
related values into the dialog.
(for most cases a simple savestate on a bean should do it)
Re: wat is the main advantage of aliasbean component
Or in other words, it can be used to effectively pass a parameter to
an included page, by making the names that the included page needs
(parameter names) point to the appropriate values.
Cagatay Civici wrote:
Hi,
In addition, here's an example that might help;
http://www.jroller.com/page/cagataycivici?entry=jsf_composition_components_with_aliasbean
http://www.jroller.com/page/cagataycivici?entry=jsf_composition_components_with_aliasbean
Regards,
Cagatay
On 1/31/07, *Gerald Müllan* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi,
the main advantage when using t:aliasBean it reusing existing pages.
Consider having a fragment page, which you want to use in other
pages. This
page fragment doesn`t access components like a dataTable per
#{managedBean.list}, it
does its job the way like #{list}.
E.g.:
t:dataTable value=#{list} ..
/t:dataTable
So, in the pages where you want to use the fragment, you can write:
t:aliasBean alias=#{list} value=#{firstManagedBean.list}
jsp:include page=pageFragment.jsp/
/t:aliasBean
The next page:
t:aliasBean alias=#{list} value=#{ secondManagedBean.list}
jsp:include page=pageFragment.jsp/
/t:aliasBean
It is a generic way of including pages by using a so called alias.
Coherent now?
cheers,
Gerald
On 1/31/07, dasara [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi All,
I'm new to MyFaces components. I could not understand how can we
make use of
t:aliasbean component.
When there is a managed bean, why to go for t:aliasbean.
Where can i find the effective use of t:aliasbean. I mean in which
situation we can go for t:aliasbean component.
When is the response writer set in the context?
I had thought the response writer was set during the restoreView phase by the viewRoot. I have a phase listener that is invoked after the restore view, then calls a handler on a component. I assumed the context would have the writer set in it, but its null at that point (unless I manually set it). Am I missing something? -- View this message in context: http://www.nabble.com/When-is-the-response-writer-set-in-the-context--tf3150941.html#a8736617 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Javscript Issues with JSF 1.2, Tomahawk 1.1.3
Bharath, Offhand, I can tell you there were some javascript changes to improve compatibility since Tomahawk 1.1.3. Some of the devs like Martin would know more on this. Just to narrow down which versions your problem is affecting, can you also try with Tomahawk 1.1.4 rc from here [1] and Tomahawk 1.1.5 nightly from here [2]? [1] http://people.apache.org/builds/myfaces/tomahawk-1.1.x/ [2] http://people.apache.org/builds/myfaces/nightly/ Regards, Jeff Bischoff Kenneth L Kurz Associates, Inc. Bharath Belagodu wrote: Using JSF 1.2 with Tomahawk 1.1.3 is causing issues with several of the components developed in our application. The dynamic menus and static menus developed using panelNavigation2 aren't working. There is javascript error detected. The javascript error is 'Object Expected'. So, I set to explore just a simple example of a commandLink. The below code has an error, I'm using the tomahawk's commandLink component. t:commandLink action=welcome f:verbatim#8250; /f:verbatim t:outputText value=Test Client / /t:commandLink Changing the t:commandLink to h:commandLink works. Is tomahawk 1.1.3 not compatible with JSF 1.2? Previously we were using myfaces-1.1.4 and it worked great. Also, another strange behavior with JSF 1.2 is that our xhtml files appear as raw files when being displayed in Mozilla browser, if I use IE 6 or IE 7 there isn't an issue. This wasn't the case with myfaces1.1.4. Thanks. -Bharath
Enable/Disable Editing of Form Fields based on User Roles
I know JSF/MyFaces has disable attribute but wondering how do i enable/disable based on user roles . My other question is how do i pass userId from JSF page to Backing Bean. Here is the situation The JSF page has userId available from Single Sign On application. Now i wanna pass this userId to the Backing Bean so that i can retrieve user roles from the database based on userId. Back to JSF form based on user roles i would like to enable/disable editing of certain form fields Any pointers/suggestion on how to do this will be highly appreciated. I am using MyFaces 1.1.4, Tomahawk 1.1.3, Sanbox, Facelets 1.1.12, Ajax4JSF 1.04, Spring, Hibernate Regards Bansi -- View this message in context: http://www.nabble.com/Enable-Disable-Editing-of-Form-Fields-based-on-User-Roles-tf3151019.html#a8736868 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Dojo widgets not working on IE
Ok I am ccing this into the devs list, some other people have to look into the issue as well! I think I found the cause of all evil regarding the non initializing components: 2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getStringInitParameter INFO: No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value /faces/myFacesExtensionResource 31.01.2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getCurrentInstance INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getBooleanInitParameter INFO: No context init parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using default value true 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getStringInitParameter INFO: No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value /faces/myFacesExtensionResource 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getCurrentInstance INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation 31.01.2007 21:46:40 org.apache.myfaces.renderkit.html.util.DefaultAddResource serveResource SCHWERWIEGEND: Error while serving resource: dojo.DojoResourceLoader/dojo.js, message : null ClientAbortException: java.net.SocketException: Broken pipe at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:103) at org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.writeResource(MyFacesResourceLoader.java:244) at org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.serveResource(MyFacesResourceLoader.java:217) at org.apache.myfaces.renderkit.html.util.DefaultAddResource.serveResource(DefaultAddResource.java:606) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:128) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:613) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:746) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:348) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:769) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:117) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:579) at org.apache.coyote.Response.doWrite(Response.java:559) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:361) ... 22 more But the funny thing is, this does not happen always, something must be going badly wrong in the resource loader, which is code I have absolutely no clue about (sorry have not touched it so far) My personal assumption is, that the ie to my knowledge chokes on resources if you do not serve the filelength upfront, under certain conditions. I have no clue why I am getting
Re: Dojo widgets not working on IE
Werner Punz wrote: I think I found the cause of all evil regarding the non initializing components: Was it money? :P My second guess is women.
Re: Dojo widgets not working on IE
Jeff Bischoff schrieb: Werner Punz wrote: I think I found the cause of all evil regarding the non initializing components: Was it money? :P My second guess is women. actually no... the mac has some problems in my case.. ;-) well close enough
Re: Dojo widgets not working on IE
Ok, I am getting closer, I upgraded the tomcat versions, the problem still persists. Funny thing is, it is only on a Mac (running an intel Dual Core) If I serve the file from linux on a single core notebook in the same Tomcat configuration the problems are gone. This looks like a timing issue, i am not sure if the mac is at fault here, or the Dual core is triggering something in the JVM, I got a similar report from a user whom I am trying to fix some issues in the Fisheye for. Anyway, dojo is not at fault here, the problem either is the jdk or some resource loader code going haiwire. The funny thing is, once I switched tomcats the client abort exception stopped (maybe it was ignored due to different settings) but the result of not working dojo controls persisted. I will add a note in the jira report, someone else has to take over that, I have to say this is beyound the domain where I am good at :-( Werner Werner Punz schrieb: Ok I am ccing this into the devs list, some other people have to look into the issue as well! I think I found the cause of all evil regarding the non initializing components: 2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getStringInitParameter INFO: No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value /faces/myFacesExtensionResource 31.01.2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getCurrentInstance INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getBooleanInitParameter INFO: No context init parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using default value true 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getStringInitParameter INFO: No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value /faces/myFacesExtensionResource 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getCurrentInstance INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation 31.01.2007 21:46:40 org.apache.myfaces.renderkit.html.util.DefaultAddResource serveResource SCHWERWIEGEND: Error while serving resource: dojo.DojoResourceLoader/dojo.js, message : null ClientAbortException: java.net.SocketException: Broken pipe at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:103) at org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.writeResource(MyFacesResourceLoader.java:244) at org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.serveResource(MyFacesResourceLoader.java:217) at org.apache.myfaces.renderkit.html.util.DefaultAddResource.serveResource(DefaultAddResource.java:606) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:128) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:613) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:746) at
RE: Javscript Issues with JSF 1.2, Tomahawk 1.1.3
Jeff, Appreciate the response. Well, the website is not reachable at this time to download 1.1.4 but I had an older copy of tomahawk 1.1.4 downloaded about 4wks ago, that seemed to work with JSF 1.2. The basic problems with commandLink, panelNavigation2 aren't occurring. Where can I find the differences between the two releases? When is tomahawk 1.1.4 going to be released? Appreciate pointers to any URLs. The problem went away but would be good to know what the problem is with tomahawk 1.1.3! Thanks. -Bharath -Original Message- From: Jeff Bischoff [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 31, 2007 3:03 PM To: MyFaces Discussion Subject: Re: Javscript Issues with JSF 1.2, Tomahawk 1.1.3 Bharath, Offhand, I can tell you there were some javascript changes to improve compatibility since Tomahawk 1.1.3. Some of the devs like Martin would know more on this. Just to narrow down which versions your problem is affecting, can you also try with Tomahawk 1.1.4 rc from here [1] and Tomahawk 1.1.5 nightly from here [2]? [1] http://people.apache.org/builds/myfaces/tomahawk-1.1.x/ [2] http://people.apache.org/builds/myfaces/nightly/ Regards, Jeff Bischoff Kenneth L Kurz Associates, Inc. Bharath Belagodu wrote: Using JSF 1.2 with Tomahawk 1.1.3 is causing issues with several of the components developed in our application. The dynamic menus and static menus developed using panelNavigation2 aren't working. There is javascript error detected. The javascript error is 'Object Expected'. So, I set to explore just a simple example of a commandLink. The below code has an error, I'm using the tomahawk's commandLink component. t:commandLink action=welcome f:verbatim#8250; /f:verbatim t:outputText value=Test Client / /t:commandLink Changing the t:commandLink to h:commandLink works. Is tomahawk 1.1.3 not compatible with JSF 1.2? Previously we were using myfaces-1.1.4 and it worked great. Also, another strange behavior with JSF 1.2 is that our xhtml files appear as raw files when being displayed in Mozilla browser, if I use IE 6 or IE 7 there isn't an issue. This wasn't the case with myfaces1.1.4. Thanks. -Bharath
Re: Javscript Issues with JSF 1.2, Tomahawk 1.1.3
Unfortunately, we weren't requiring JIRA issues with every change last June. The following commit log is the best you can do for seeing what happened to make Tomahawk 1.1.4 compatible with the RI. http://svn.apache.org/viewvc?view=revrevision=422260 On 1/31/07, Bharath Belagodu [EMAIL PROTECTED] wrote: Jeff, Appreciate the response. Well, the website is not reachable at this time to download 1.1.4 but I had an older copy of tomahawk 1.1.4 downloaded about 4wks ago, that seemed to work with JSF 1.2. The basic problems with commandLink, panelNavigation2 aren't occurring. Where can I find the differences between the two releases? When is tomahawk 1.1.4 going to be released? Appreciate pointers to any URLs. The problem went away but would be good to know what the problem is with tomahawk 1.1.3! Thanks. -Bharath -Original Message- From: Jeff Bischoff [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 31, 2007 3:03 PM To: MyFaces Discussion Subject: Re: Javscript Issues with JSF 1.2, Tomahawk 1.1.3 Bharath, Offhand, I can tell you there were some javascript changes to improve compatibility since Tomahawk 1.1.3. Some of the devs like Martin would know more on this. Just to narrow down which versions your problem is affecting, can you also try with Tomahawk 1.1.4 rc from here [1] and Tomahawk 1.1.5 nightly from here [2]? [1] http://people.apache.org/builds/myfaces/tomahawk-1.1.x/ [2] http://people.apache.org/builds/myfaces/nightly/ Regards, Jeff Bischoff Kenneth L Kurz Associates, Inc. Bharath Belagodu wrote: Using JSF 1.2 with Tomahawk 1.1.3 is causing issues with several of the components developed in our application. The dynamic menus and static menus developed using panelNavigation2 aren't working. There is javascript error detected. The javascript error is 'Object Expected'. So, I set to explore just a simple example of a commandLink. The below code has an error, I'm using the tomahawk's commandLink component. t:commandLink action=welcome f:verbatim#8250; /f:verbatim t:outputText value=Test Client / /t:commandLink Changing the t:commandLink to h:commandLink works. Is tomahawk 1.1.3 not compatible with JSF 1.2? Previously we were using myfaces-1.1.4 and it worked great. Also, another strange behavior with JSF 1.2 is that our xhtml files appear as raw files when being displayed in Mozilla browser, if I use IE 6 or IE 7 there isn't an issue. This wasn't the case with myfaces1.1.4. Thanks. -Bharath
Tobago server-side/ajax
Hi! Does anyone have a working solution for a server-side/ajaxized tobago tree? If not: Any idea how to extend the classes to catch the expand/collapse node event? Regards Sebastian -- View this message in context: http://www.nabble.com/Tobago-server-side-ajax-tf3152221.html#a8740722 Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: Re: Dojo widgets not working on IE
Please update when this fix is available. I am in the process of testing a fix for scrolling dialog boxes and this error is now preventing me from testing my fix. Regards, Joshua Pheneger -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz Sent: Wednesday, January 31, 2007 2:00 PM To: users@myfaces.apache.org Subject: Re: Dojo widgets not working on IE Ok, I am getting closer, I upgraded the tomcat versions, the problem still persists. Funny thing is, it is only on a Mac (running an intel Dual Core) If I serve the file from linux on a single core notebook in the same Tomcat configuration the problems are gone. This looks like a timing issue, i am not sure if the mac is at fault here, or the Dual core is triggering something in the JVM, I got a similar report from a user whom I am trying to fix some issues in the Fisheye for. Anyway, dojo is not at fault here, the problem either is the jdk or some resource loader code going haiwire. The funny thing is, once I switched tomcats the client abort exception stopped (maybe it was ignored due to different settings) but the result of not working dojo controls persisted. I will add a note in the jira report, someone else has to take over that, I have to say this is beyound the domain where I am good at :-( Werner Werner Punz schrieb: Ok I am ccing this into the devs list, some other people have to look into the issue as well! I think I found the cause of all evil regarding the non initializing components: 2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getStringInitParameter INFO: No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value /faces/myFacesExtensionResource 31.01.2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getCurrentInstance INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getBooleanInitParameter INFO: No context init parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using default value true 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getStringInitParameter INFO: No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value /faces/myFacesExtensionResource 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig getCurrentInstance INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation 31.01.2007 21:46:40 org.apache.myfaces.renderkit.html.util.DefaultAddResource serveResource SCHWERWIEGEND: Error while serving resource: dojo.DojoResourceLoader/dojo.js, message : null ClientAbortException: java.net.SocketException: Broken pipe at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.j ava:366) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314 ) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStrea m.java:103) at org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.writeResour ce(MyFacesResourceLoader.java:244) at org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.serveResour ce(MyFacesResourceLoader.java:217) at org.apache.myfaces.renderkit.html.util.DefaultAddResource.serveResource( DefaultAddResource.java:606) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFil ter.java:128) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1 48) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86 9) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc essConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint .java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow erWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:684) at
RE: Re: modalDialog scrolls endlessly on page
I believe I have verified that this is a layering issue. I create two modal
dialogs in an identical fashion and access them in the following way:
Page contains commandLink1 to first modalDialog1.
modalDialog1 contains a commandLink2 to modalDialog2.
Clicking on commandLink1 will cause modalDialog1 to appear. I am unable to
select any text behind the dialog.
Clicking on commandLink2 (from within modalDialog1) will cause modalDialog2 to
appear on top of modalDialog1.
I am able to select the text within modalDialog1 while modalDialog2 is visible.
At this point, I am unable to type into the text field in modalDialog2
(h:inputText component). I am able to click on the commandButton in
modalDialog1 and close modalDialog1 while modalDialog2 is still open. Once
modalDialog1 is closed modalDialog2's text field is now editable.
Regards,
Joshua Pheneger
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz
Sent: Wednesday, January 31, 2007 11:54 AM
To: users@myfaces.apache.org
Subject: Re: modalDialog scrolls endlessly on page
Ok I only see one problem
you mix and match html input fields
with jsf forms there ,
I am not sure how facelets behave
there, but you ask for trouble regarding other stuff (like automatic value
assigment, automatic validation etc...) try to replace your simple input field
with the jsf equivalent h:inputText or t:inputText.
What should happen is, first, you should be able to edit the fields secondly,
you should be able to submit the form, and get the values into the beans
assigned to the field.
Check the tomahawk-sandbox-examples for exactly this usecase, like gerald
pointed it out.
As for stacking dialogs, yes it is possible, but i do not know how it behaves
formwise, but I assume following first dialog has a form, second one is opened
after the first one, it should be stacked on top of the first one also has a
form, you submit the form in the second dialog and trigger a page refresh, the
values of the second form should be assigned to the backend beans, and you will
basically lose both dialogs, the changed values of the first dialog will be
lost however!.
Joshua Pheneger schrieb:
I will file a bug with the dojo team to investigate the dialog scrolling
issue.
Can you clarify your response on the form text field issue? Is it
possible/recommended to use a form within a dialog that is sitting on top of
another dialog? What would the code look like? The following code does not
allow the text field to be edited.
b:modalDialog dialogId=TripDatesDialogContent dialogVar=tripDatesDialog
dialogAttr=bgColor='white' bgOpacity='0.5' toggle='fade'
toggleDuration='250'
hiderIds=cancel2 styleClass=dojoDialog
h:form
h:panelGrid
input type=text name=something value=myvalue
id=newdates size=25/
b:commandButton id=cancel2 forceId=true
value=Cancel
onclick=dojo.widget.byId('TripDatesDialogContent').hide(); /
/h:panelGrid
/h:form
/b:modalDialog
Regards,
Joshua Pheneger
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz
Sent: Wednesday, January 31, 2007 8:22 AM
To: users@myfaces.apache.org
Subject: Re: modalDialog scrolls endlessly on page
Gerald Müllan schrieb:
Hi,
the modalDialog component uses the dojo js-lib dialog widget. Any js
related problems can not be solved by myfaces developers, they are
only dojo-related. Maybe you can find help with this issue on the
dojo list.
The dialog issue is an issue with the dojo dialog itself, there is a
parameter in the dojo baselib which can prevent this behavior (it is
called centerdialog or so, you really have to check the dialog sources
for this) I rember having such a param at least in dojo 0.4.1 which is
the latest currently being in tomahawk
I am not sure if it already is exposed.
There also is the possibility to use floating panes instead of the dialog.
Apart from this, it maybe an issue you can live with; i also use the
modalDialog in an application and it works very well.
The current sandbox snapshot with the dialog component is deployed here:
http://example.irian.at/example-sandbox-20070131/dojo/dojoDialog.jsf
If you click on searchOuterForm, the dialog accomplishes the same
usecase as you have with the form. Seems to work there.Have a look at
the source of the example, maybe it can assist.
What you mean by unable to enter? Are the input fields hidden, or
disabled? Does the post not happen?
The code looks to me as if the form is declared outside of the dialog this is
not possible due to browser limitations, mainly caused by the broken ie css
implementation.
If you want to use the dialog in conjunction with forms use it outside of any
form definition and put the form into the dialog, there are various ways to
savestate the affected
Re: Creating customized components
Are there any documents for creating/extending components to create customized components? Regards, Joshua Pheneger
jscookMenu with outputLink
Hi, Is there any way to use jscookMenu with a basic url instead of having to declare an action navigation rule? Thanks for great stuff, Ken
jscookMenu with outputLink?
Hi, Is there any way to use jscookMenu with a basic url instead of having to declare an action navigation rule? Thanks, Ken
Myfaces 1.1.1 - Myfaces 1.1.5 migration question
Is the MyFaces 1.1.5 snapshot production stable? Would you put it in a production environment? If not, which version would you recommend me to upgrade to? Thanks - Make free worldwide PC-to-PC calls. Try the new Yahoo! Canada Messenger with Voice
Trinidad myfaces compatibility
Which version of myfaces is compatible with the current Trinidad snapshot? Thanks again - Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail
Re: Trinidad myfaces compatibility
Just to be precise, in both my messages when I said myfaces I meant myfaces core + tomahawk. I extensively use tomahawk in my project. I am looking to use some of the trinidad components, and I want to know which versions of myfaces core tomahawk trinidad is compatible with. I found this link but it doesn't specify trinidad: http://wiki.apache.org/myfaces/CompatibilityMatrix Costa Basil [EMAIL PROTECTED] wrote: Which version of myfaces is compatible with the current Trinidad snapshot? Thanks again - Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail - Now you can have a huge leap forward in email: get the new Yahoo! Mail.
sandBox not working
hai all, iam working on sand box components. 1.tomahawk-sandbox-1.1.5-SNAPSHOT.jar 2.tomahawk-sandbox-1.1.5-SNAPSHOT-sources.jar i added these 2 jar files. javax.faces.FacesException: javax.servlet.ServletException: Missing class: org.apache.myfaces.custom.dojo.DojoConfig Dependent class: org.apache.myfaces.custom.effect.EffectRenderer Loader: current-workspace-app.web.ViewController:0.0.0 Code-Source: /home/developer/jdevhome/mywork/TomahawkComponents/ViewController/public_html/WEB-INF/lib/tomahawk-sandbox-1.1.5-SNAPSHOT.jar Configuration: WEB-INF/lib/ directory in /home/developer/jdevhome/mywork/TomahawkComponents/ViewController/public_html/WEB-INF/lib The missing class is not available from any code-source or loader in the system. at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:351) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:152) at oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:157) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:107) -- View this message in context: http://www.nabble.com/sandBox-not-working-tf3153109.html#a8743237 Sent from the MyFaces - Users mailing list archive at Nabble.com.
What's the use of Icon provider component
Hi All, how to use icon provider. AND What's the use of Icon provider component plz help me THANKS... -- View this message in context: http://www.nabble.com/What%27s-the-use-of-Icon-provider-component-tf3153267.html#a8743716 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: sandBox not working
Hi Which version of tomahawk itself are you using? Regards, Cagatay On 2/1/07, jaguar [EMAIL PROTECTED] wrote: hai all, iam working on sand box components. 1.tomahawk-sandbox-1.1.5-SNAPSHOT.jar 2.tomahawk-sandbox-1.1.5-SNAPSHOT-sources.jar i added these 2 jar files. javax.faces.FacesException: javax.servlet.ServletException: Missing class: org.apache.myfaces.custom.dojo.DojoConfig Dependent class: org.apache.myfaces.custom.effect.EffectRenderer Loader: current-workspace-app.web.ViewController:0.0.0 Code-Source: /home/developer/jdevhome/mywork/TomahawkComponents/ViewController/public_html/WEB-INF/lib/tomahawk- sandbox-1.1.5-SNAPSHOT.jar Configuration: WEB-INF/lib/ directory in /home/developer/jdevhome/mywork/TomahawkComponents/ViewController/public_html/WEB-INF/lib The missing class is not available from any code-source or loader in the system. at com.sun.faces.context.ExternalContextImpl.dispatch( ExternalContextImpl.java:351) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java :152) at oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView( ViewHandlerImpl.java:157) at com.sun.faces.lifecycle.RenderResponsePhase.execute( RenderResponsePhase.java:107) -- View this message in context: http://www.nabble.com/sandBox-not-working-tf3153109.html#a8743237 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Myfaces 1.1.1 - Myfaces 1.1.5 migration question
Hi, We're using 1.1.5 snapshot with no problems in production. Cagatay On 2/1/07, Costa Basil [EMAIL PROTECTED] wrote: Is the MyFaces 1.1.5 snapshot production stable? Would you put it in a production environment? If not, which version would you recommend me to upgrade to? Thanks -- Make free worldwide PC-to-PC calls. Try the new *Yahoo! Canada Messenger with Voice* http://ca.messenger.yahoo.com/
Re: Tobago Not working in JDev(OC4J)
Hello Samba, Tobago does't work very well with other renderkits. see: http://myfaces.apache.org/tobago/faq.html#tobago/myfaces%20extension Can you open an issue in Jira with the complete StackTrace and the oc4j version or jdev version. http://myfaces.apache.org/tobago/issue-tracking.html Regards Bernd Samba wrote: Hello everybody, I'm new to my faces. I'm trying to use trinidad ,tomahawk and tobago together in the same application. But first things first. I'm able to work with trinidad, and tomahawk individually;but I'm getting problem with integrating them getting the error : No RenderingContext And then I tried my luck with tobago ,with out any other libraries. Some of the components,like label,out,textArea , are working but most of the the components are giving me error : javax.servlet.ServletException: InValid to flush BodyContent: no backing stream behind it I'm JDeveloper with Embedded OC4J running in it. Can you please help me fix the issue? Thanking you in advance, Samba.
Re: sandBox not working
hai cagatay, thanks for reply, i am using tomahawak version1.1.3. and myfaces 1.1.4. i hope this can help me. thanks, regards, satish Cagatay Civici wrote: Hi Which version of tomahawk itself are you using? Regards, Cagatay On 2/1/07, jaguar [EMAIL PROTECTED] wrote: hai all, iam working on sand box components. 1.tomahawk-sandbox-1.1.5-SNAPSHOT.jar 2.tomahawk-sandbox-1.1.5-SNAPSHOT-sources.jar i added these 2 jar files. javax.faces.FacesException: javax.servlet.ServletException: Missing class: org.apache.myfaces.custom.dojo.DojoConfig Dependent class: org.apache.myfaces.custom.effect.EffectRenderer Loader: current-workspace-app.web.ViewController:0.0.0 Code-Source: /home/developer/jdevhome/mywork/TomahawkComponents/ViewController/public_html/WEB-INF/lib/tomahawk- sandbox-1.1.5-SNAPSHOT.jar Configuration: WEB-INF/lib/ directory in /home/developer/jdevhome/mywork/TomahawkComponents/ViewController/public_html/WEB-INF/lib The missing class is not available from any code-source or loader in the system. at com.sun.faces.context.ExternalContextImpl.dispatch( ExternalContextImpl.java:351) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java :152) at oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView( ViewHandlerImpl.java:157) at com.sun.faces.lifecycle.RenderResponsePhase.execute( RenderResponsePhase.java:107) -- View this message in context: http://www.nabble.com/sandBox-not-working-tf3153109.html#a8743237 Sent from the MyFaces - Users mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/sandBox-not-working-tf3153109.html#a8744198 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Dojo widgets not working on IE
Joshua Pheneger schrieb: Please update when this fix is available. I am in the process of testing a fix for scrolling dialog boxes and this error is now preventing me from testing my fix. Regards, Joshua Pheneger Jousha I am still trying to figure some things out here, what is the configuration does your server run on? The reason why I am asking is, because I want to know if this is a dual core/multi core issue or some problems with the Mac JDK or (or a bug triggered in it)
Re: modalDialog scrolls endlessly on page
Joshua Pheneger schrieb: I believe I have verified that this is a layering issue. I create two modal dialogs in an identical fashion and access them in the following way: Page contains commandLink1 to first modalDialog1. modalDialog1 contains a commandLink2 to modalDialog2. Clicking on commandLink1 will cause modalDialog1 to appear. I am unable to select any text behind the dialog. Clicking on commandLink2 (from within modalDialog1) will cause modalDialog2 to appear on top of modalDialog1. I am able to select the text within modalDialog1 while modalDialog2 is visible. At this point, I am unable to type into the text field in modalDialog2 (h:inputText component). I am able to click on the commandButton in modalDialog1 and close modalDialog1 while modalDialog2 is still open. Once modalDialog1 is closed modalDialog2's text field is now editable. Regards, Joshua Pheneger Yes this is a layering issue indeed, this has to be fixed on the dojo side, I have never used stacked dialogs that way, sorry to say that, anyway you might get a workaround a different way, hide the first dialog before displaying the second then the stacking issue should dissapear, due to the way the dialog behaves. The dialogs work the following way: Push a div over everything to basically grey out the entire area Push the dialog div on top of the greying div. To display the dialog. That is also the reason why forms do not work outside of dialogs. The code has to push the dialog div on the beginning or end of the body definitions because outside forms can interfere with position absolute on some browsers, and the logical choice position fixed does not work at all on ie6! Also there are floating frames in the dojo code (I think they already are componentized, check the dojo subdir of the sandbox) To my knowledge they also can be made modal, so you might get to the desired results with them. Werner
