Tobago causes javaScript error
Title: Tobago causes javaScript error Tobago team, We are using tobago version dated 03/22/2006 and have lots of _javascript_ errors in _javascript_ Console while working with toolbars. Under Firefox error looks like the following: Error: this.images[id] has no properties Source File: http://nstasiv:8080/bpms-console/tobago/html/standard/standard/script/tobago.js Line: 312 (Tobago.toolbarMousesover() function in tobago.js) Error also appears under IE and looks like this: Line:324 Char:5 Error: 'this.images[...].normal' is null or is not an object Although this does not affect functionality and the toolbar bahaves correctly. Can you explain this problem? Thanks, Ira
tobago stable release
Tobago team, When are you going to make stable official release? We would like our application to stick to some definite version and not to update tobago and deal with changes (like deprecated components) every time something is changed or fixed. Releases would also give release notes and list of what have been done. Thanks, Ira
Tobago t:link behaves oddly under IE
Hi, I have t:link on the page which redirects to some other page (navigate). Sometimes if I click on it under IE once the page will remain unchanged (no action performed). It will only work if I click on it once again. The problem does not exist under Firefox. I am using trunk version of tobago. (I am not sure if this problem existed in previous revisions) Thanks, Ira
Need target attribute for Tobago t:toolBarCommand
Hello, I need something like "target" attribute for t:toolBarCommand component. The aim is to open the result of the action execution in e.g new window(target=blank). Using type="script" will not satisfy me, because I need the backing bean action being executed, and then the result being opened in a separate window (result depends on the action). Is there any solution?? Thanks, Ira
Re: JSF navigation url problem
Hello Anthony, I've been fighting with this problem for long. I'm afraid you cannot be offered any good solution now. Look here http://issues.apache.org/jira/browse/TOBAGO-2 for our company's ideas on how to solve it. Thursday, March 2, 2006, 4:19:33 PM, you wrote: > In JSF navigation rule, show as following > > /pages/inputname.jsp > > sayHello > /pages/greeting.jsp > > > sayGoodbye > /pages/goodbye.jsp > > > In this example, click button in inputname.jsp can change page to > greeting.jsp, but the url in IE has no change, means it is as same > "inputname.jsp", click link in greeting.jsp to goodbye.jsp, url in IE > is "greeting.jsp" > Seams it is always one step after current page. it works fine by click > link. but if I refresh current page, it displayed previous page not > current page. > This can be solved by add in each navigation-case. But why > default action has such problem? What is the purpose? > -- > Anthony Hong -- Best regards, Iryna mailto:[EMAIL PROTECTED] ICQ #: 150867790
Re[2]: Tobago t:toolBarCommand
Volker, Thank you. One more question. Can I have something like "target=blank" attribute for button with submit (i.e. to open the result of the action performed in a new window) ? Please help Thursday, March 2, 2006, 2:33:50 PM, you wrote: > Hi Iryna, > Iryna Stetska wrote: >> Hello, >> >> I have 2 questions on Tobago toolBarCommand component. >> >> 1. How can I implement functionality on both executing script and >> executing action of the backing bean while pressing the toolbar >> button? >> This mean that if I press the toolbar button some java script should >> be executed (e.g. showing alert) and then the bean action should be >> executed. >> Can it be somehow implemented? > If you want to show a confirm dialog you can add a confirmation facet: > > > > > > For other things you must use type="script" and call the default submit > function (see onclick attribute of generated html buttons) yourself. >> >> 2. What can I write in the toolBarCommand Body? >> Is this code implemented only after pressing this button or always? >> Please explain. >> >> BODY >> > Any body content of toolBarCommand, except some special facets (see > above) is ignored. >> >> Thanks, >> Iryna >> > Regards, > Volker -- Best regards, Iryna mailto:[EMAIL PROTECTED] ICQ #: 150867790
Tobago t:toolBarCommand
Hello, I have 2 questions on Tobago toolBarCommand component. 1. How can I implement functionality on both executing script and executing action of the backing bean while pressing the toolbar button? This mean that if I press the toolbar button some java script should be executed (e.g. showing alert) and then the bean action should be executed. Can it be somehow implemented? 2. What can I write in the toolBarCommand Body? Is this code implemented only after pressing this button or always? Please explain. BODY Thanks, Iryna
tobato t:sheet sorting
We are using t:sheet component. We need to implement sortable column in it which would perform sorting by clicking on the column header, while sorting will be performed on the server side. (We don't want to use standard tobago sheet sorting for substantial reason). Can we have some event handler implemented for clicking the t:sheet column header?
Tobago t:in (IllegalArgumentException: empty expr)
t:in producess java.lang.IllegalArgumentException: empty expr
I experienced java.lang.IllegalArgumentException: empty expr
When pressing ENTER in t:in component. #{instances.pagingLength} value
binding is of type int and actual value was 40
java.lang.IllegalArgumentException: empty expr at
javax.faces.component.UIComponentBase.findComponent(UIComponentBase.java:211)
at
org.apache.myfaces.tobago.component.UIPage.processDecodes(UIPage.java:158)
at
javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:397)
at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:131)
at
org.apache.myfaces.tobago.component.UIViewRoot.processDecodes(UIViewRoot.java:174)
at
org.apache.myfaces.lifecycle.LifecycleImpl.applyRequestValues(LifecycleImpl.java:177)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:71)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:94) at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427)
at
org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:99)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:832)
at
org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:171)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:272) at
org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:169) at
com.intalio.bpms.console.rest.rules.RulesEngine.doForward(RulesEngine.java:97)
at
com.intalio.bpms.console.rest.rules.RulesEngine.doForward(RulesEngine.java:72)
at
com.intalio.bpms.console.rest.RESTFilter.doFilter(RESTFilter.java:199)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
at
org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:171)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) at
org.mortbay.http.HttpServer.service(HttpServer.java:954) at
org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Re[2]: Tobago sheet sorting
HI, I tried using construction like this: In this case the links are not displayed, just labels instead (not clickable). Please help > Hi Olexandr, > First: please don't use SortableByApplication, this will be removed. > We are thinking about to allow applications to register a eventListener > to recieve sort events and do the sorting there. > Now to your problem: > Currently sorting of links should work if you use a t:label tag inside > the t:link instead of the label attribute. > I think the sorting code is older than the label attibute on the link tag. > Please oben a jira issue to support this. > Regards, > Volker > Olexandr Zakordonskyy wrote: >> Hi Tobago Team. >> >> Help me with sorting column which contains t:link component. >> In sorter there is a todo: >> >> // TODO: locale / comparator parameter? >> // don't compare numbers with Collator.getInstance() comparator >> //Comparator comparator = Collator.getInstance(); >> // comparator = new RowComparator(ascending, method); >> >> >> It may be possible to use SortableByApplication, but >> Line 156 is commented >> >> Please, help. >> >> Thanks, >> Olexandr. >> -- Best regards, Iryna mailto:[EMAIL PROTECTED] ICQ #: 150867790
Tobago t:tree : visual indicator for the current node.
I'm using t:tree. I would like to have some visual indicator (different backgroung, color or style) for the tree node currently selected (which is changed when TreeState.setMarker(DefaultMutableTreeNode node) is called). Is it possible??
Tobago t:link underline
HI, I have the following structure Links in the first column should be underlined, in second column - not underlined. Can I implement it? Did you consider specifying "class" or "style" attribute for t:link and maybe other components. Thanks
Tobago bugs
Hi, Our company is developing application using Tobago. I'm sending you a list of bugs / enhancements we came across recently. Please give some feedback. 1. t:forEach (bug) Component does not work with Iterables. It seems that it analyzes only one record. For now we can only use t:sheet to iterate Collections, but it would be better to have t:forEach functional. The disadvantages of using t:sheet in this case are the following: - selecting rows and highlighing them with different color - impossibility to set auto height - vertical scrolls appearing - light background - components do not fit the whole width, leaving space on the right 2. t:sheet (enhancement) There should be possibility to specify component auto height (analog for "100%" in html). This functionality is necessary to avoid scrollbars(when we have many records) and ugly dark grey background(when we have not enough records to fit the specified height). So we need the t:sheet component to "autostretch" depending on the number of records. 3. t:tabGroup (bug) Active tab status is not saved and is lost after page refresh. 4. t:image (bug) Alt attribute is not functional. Setting this attribute has no effect at all. Thanks, Ira
