Re: CommandLink in dataTabl
Hi Radu, you've run into a compatibility problem between Sun RI 1.1 and Tomahawk, both in earlier versions. An upgrade to the latest 1.1 version of both libraries should help! regards, Martin On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: > > Hello, > I am a newbie learning JSF while trying to meet deadlines on a JSF > refactoring project. > The docs & forums have helped me quite a lot untill now when I seem to > be facing > a wierd problem. Here is the context : I have a dataTable and a commandLink > on every > line. The actionListener associated with this commandLink should only update > some db information > for the concerned record(and then redisplay the same page again). > My problem is that when i click on _one_ link the actionListener is called > for every link from the dataTable. > It is just like had clicked _all_ the links!! very weird. > (If I have 30 links displayed, I click one link and the actionListener is > called 30 times.. for > all 30 rows) > > Environement : > app server : WebLogic 8.1 SP4 > jsf implementation : SUN RI 1.1 > tomahawk version : 1.1.1 (the only one working with weblogic 8.1) > > ---THE VIEW--- > #adminLogging.jsp## > > > value="#{logSort.loggers}" > var="log" > binding="#{logSort.dataTable}" > sortColumn="#{logSort.sort}" > sortAscending="#{ logSort.ascending}" > preserveSort="true" > > > > > > > > > > > > > > > > actionListener="#{logSort.modifyLogOnServer3}"/> > > > > > ## > > > ---BACKING BEAN--- > public class LogSortHelper extends SortableList{ > > private HtmlDataTable dataTable; > > public void modifyLogOnServer3(javax.faces.event.ActionEvent event) { > > LoggerBean row = (LoggerBean) dataTable.getRowData(); > String attributeName = row.getLoggerName(); > logger.debug("atribute Name:"+attributeName+"|"); > } > ... > } > > ---LOGGERBEAN--- > public class LoggerBean { > ... > private String loggerName ; > > } > > > in faces-config.xml, logSort = LogSortHelper > > > > Further on , I've tryed to get rid of the component binding stuff... (which > in fact I only needed > for the dataTable.getRowData() method) . > > So i did the following modifications : > (http://wiki.apache.org/myfaces/ExecutingMethodsFromLinkButtonParameters) > > ---VIEW--- > actionListener="#{logSort.modifyLogOnServer4}"> > value="#{log.loggerName}"/> > > > > ---BACKING BEAN--- > > public String modifyLogOnServer4(javax.faces.event.ActionEvent event) { > FacesContext context = FacesContext.getCurrentInstance(); > Map map = context.getExternalContext().getRequestParameterMap(); > String attributeName = (String) map.get("logDebugId"); > } > > Now I have my actionListener called 30 times... but for the same link( not > anymore for all the links > in the dataTable, but for the same link... 30 times) > > > And then something else : I am having inconsistent behaviour when changing > from commandButton to commandLink... > IE : using commandButton my parameter is not passed to the backing > bean.(with commandLink I see params > in the backing bean) > > Anybody got any solutions? > > Regards, > Radu Milos > > > > -- > View this message in context: > http://www.nabble.com/CommandLink-in-dataTabl-tf4370964.html#a12458281 > 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: CommandLink in dataTabl
First, thanks for the interest. Problem is that with WebLogic 8.1(this is my constrain) I am stuck to sun RI 1.1 and tomahawk 1.1.1 I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I couldn't get them working. Radu Martin Marinschek wrote: > > Hi Radu, > > you've run into a compatibility problem between Sun RI 1.1 and > Tomahawk, both in earlier versions. An upgrade to the latest 1.1 > version of both libraries should help! > > regards, > > Martin > > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: >> >> Hello, >> I am a newbie learning JSF while trying to meet deadlines on a JSF >> refactoring project. >> The docs & forums have helped me quite a lot untill now when I seem >> to >> be facing >> a wierd problem. Here is the context : I have a dataTable and a >> commandLink >> on every >> line. The actionListener associated with this commandLink should only >> update >> some db information >> for the concerned record(and then redisplay the same page again). >> My problem is that when i click on _one_ link the actionListener is >> called >> for every link from the dataTable. >> It is just like had clicked _all_ the links!! very weird. >> (If I have 30 links displayed, I click one link and the actionListener is >> called 30 times.. for >> all 30 rows) >> >> Environement : >> app server : WebLogic 8.1 SP4 >> jsf implementation : SUN RI 1.1 >> tomahawk version : 1.1.1 (the only one working with weblogic 8.1) >> >> ---THE VIEW--- >> #adminLogging.jsp## >> >> >> > value="#{logSort.loggers}" >> var="log" >> binding="#{logSort.dataTable}" >> sortColumn="#{logSort.sort}" >> sortAscending="#{ logSort.ascending}" >> preserveSort="true" >> > >> >> >>> > >> >> >> >> >> >> >> >> >> >> >> > actionListener="#{logSort.modifyLogOnServer3}"/> >> >> >> >> >> ## >> >> >> ---BACKING BEAN--- >> public class LogSortHelper extends SortableList{ >> >> private HtmlDataTable dataTable; >> >> public void modifyLogOnServer3(javax.faces.event.ActionEvent event) { >> >> LoggerBean row = (LoggerBean) dataTable.getRowData(); >> String attributeName = row.getLoggerName(); >> logger.debug("atribute Name:"+attributeName+"|"); >> } >> ... >> } >> >> ---LOGGERBEAN--- >> public class LoggerBean { >> ... >> private String loggerName ; >> >> } >> >> >> in faces-config.xml, logSort = LogSortHelper >> >> >> >> Further on , I've tryed to get rid of the component binding stuff... >> (which >> in fact I only needed >> for the dataTable.getRowData() method) . >> >> So i did the following modifications : >> (http://wiki.apache.org/myfaces/ExecutingMethodsFromLinkButtonParameters) >> >> ---VIEW--- >> > actionListener="#{logSort.modifyLogOnServer4}"> >> > value="#{log.loggerName}"/> >> >> >> >> ---BACKING BEAN--- >> >> public String modifyLogOnServer4(javax.faces.event.ActionEvent event) { >> FacesContext context = FacesContext.getCurrentInstance(); >> Map map = context.getExternalContext().getRequestParameterMap(); >> String attributeName = (String) map.get("logDebugId"); >> } >> >> Now I have my actionListener called 30 times... but for the same link( >> not >> anymore for all the links >> in the dataTable, but for the same link... 30 times) >> >> >> And then something else : I am having inconsistent behaviour when >> changing >> from commandButton to commandLink... >> IE : using commandButton my parameter is not passed to the backing >> bean.(with commandLink I see params >> in the backing bean) >> >> Anybody got any solutions? >> >> Regards, >> Radu Milos >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/CommandLink-in-dataTabl-tf4370964.html#a12458281 >> 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 > > -- View this message in context: http://www.nabble.com/CommandLink-in-dataTabl-tf4370964.html#a12458540 Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: CommandLink in dataTabl
Hi Radu, Not sure why this problem exists, however a quick way to get rid of this could be passing a parameter (f:param) along with the command link; get this parameter in the action listener and then perform the necessary operation. ~Sandeep -Original Message- From: radu_milos [mailto:[EMAIL PROTECTED] Sent: Monday, September 03, 2007 2:55 PM To: users@myfaces.apache.org Subject: Re: CommandLink in dataTabl First, thanks for the interest. Problem is that with WebLogic 8.1(this is my constrain) I am stuck to sun RI 1.1 and tomahawk 1.1.1 I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I couldn't get them working. Radu Martin Marinschek wrote: > > Hi Radu, > > you've run into a compatibility problem between Sun RI 1.1 and > Tomahawk, both in earlier versions. An upgrade to the latest 1.1 > version of both libraries should help! > > regards, > > Martin > > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: >> >> Hello, >> I am a newbie learning JSF while trying to meet deadlines on a JSF >> refactoring project. >> The docs & forums have helped me quite a lot untill now when I seem >> to >> be facing >> a wierd problem. Here is the context : I have a dataTable and a >> commandLink >> on every >> line. The actionListener associated with this commandLink should only >> update >> some db information >> for the concerned record(and then redisplay the same page again). >> My problem is that when i click on _one_ link the actionListener is >> called >> for every link from the dataTable. >> It is just like had clicked _all_ the links!! very weird. >> (If I have 30 links displayed, I click one link and the actionListener is >> called 30 times.. for >> all 30 rows) >> >> Environement : >> app server : WebLogic 8.1 SP4 >> jsf implementation : SUN RI 1.1 >> tomahawk version : 1.1.1 (the only one working with weblogic 8.1) >> >> ---THE VIEW--- >> #adminLogging.jsp### ### >> >> >> > value="#{logSort.loggers}" >> var="log" >> binding="#{logSort.dataTable}" >> sortColumn="#{logSort.sort}" >> sortAscending="#{ logSort.ascending}" >> preserveSort="true" >> > >> >> >>> > >> >> >> >> >> >> >> >> >> >> >> > actionListener="#{logSort.modifyLogOnServer3}"/> >> >> >> >> >> ## >> >> >> ---BACKING BEAN--- >> public class LogSortHelper extends SortableList{ >> >> private HtmlDataTable dataTable; >> >> public void modifyLogOnServer3(javax.faces.event.ActionEvent event) { >> >> LoggerBean row = (LoggerBean) dataTable.getRowData(); >> String attributeName = row.getLoggerName(); >> logger.debug("atribute Name:"+attributeName+"|"); >> } >> ... >> } >> >> ---LOGGERBEAN--- >> public class LoggerBean { >> ... >> private String loggerName ; >> >> } >> >> >> in faces-config.xml, logSort = LogSortHelper >> >> >> >> Further on , I've tryed to get rid of the component binding stuff... >> (which >> in fact I only needed >> for the dataTable.getRowData() method) . >> >> So i did the following modifications : >> (http://wiki.apache.org/myfaces/ExecutingMethodsFromLinkButtonParameters ) >> >> ---VIEW--- >> > actionListener="#{logSort.modifyLogOnServer4}"> >> > value="#{log.loggerName}"/> >> >> >> >> ---BACKING BEAN--- >> >> public String modifyLogOnServer4(javax.faces.event.ActionEvent event) { >> FacesContext context = FacesContext.getCurrentInstance(); >> Map map = context.getExternalContext().getRequestParameterMap(); >> String attributeName = (String) map.get("logDebugId"); >
Re: CommandLink in dataTabl
what where the problems with these other versions? We should probably better fix these... regards, Martin On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: > > First, thanks for the interest. > Problem is that with WebLogic 8.1(this is my constrain) I am stuck to sun > RI 1.1 and tomahawk 1.1.1 > I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I > couldn't get them working. > > Radu > > > Martin Marinschek wrote: > > > > Hi Radu, > > > > you've run into a compatibility problem between Sun RI 1.1 and > > Tomahawk, both in earlier versions. An upgrade to the latest 1.1 > > version of both libraries should help! > > > > regards, > > > > Martin > > > > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: > >> > >> Hello, > >> I am a newbie learning JSF while trying to meet deadlines on a JSF > >> refactoring project. > >> The docs & forums have helped me quite a lot untill now when I seem > >> to > >> be facing > >> a wierd problem. Here is the context : I have a dataTable and a > >> commandLink > >> on every > >> line. The actionListener associated with this commandLink should only > >> update > >> some db information > >> for the concerned record(and then redisplay the same page again). > >> My problem is that when i click on _one_ link the actionListener is > >> called > >> for every link from the dataTable. > >> It is just like had clicked _all_ the links!! very weird. > >> (If I have 30 links displayed, I click one link and the actionListener is > >> called 30 times.. for > >> all 30 rows) > >> > >> Environement : > >> app server : WebLogic 8.1 SP4 > >> jsf implementation : SUN RI 1.1 > >> tomahawk version : 1.1.1 (the only one working with weblogic 8.1) > >> > >> ---THE VIEW--- > >> #adminLogging.jsp## > >> > >> > >> >> value="#{logSort.loggers}" > >> var="log" > >> binding="#{logSort.dataTable}" > >> sortColumn="#{logSort.sort}" > >> sortAscending="#{ logSort.ascending}" > >> preserveSort="true" > >> > > >> > >> > >> >> > > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> >> actionListener="#{logSort.modifyLogOnServer3}"/> > >> > >> > >> > >> > >> ## > >> > >> > >> ---BACKING BEAN--- > >> public class LogSortHelper extends SortableList{ > >> > >> private HtmlDataTable dataTable; > >> > >> public void modifyLogOnServer3(javax.faces.event.ActionEvent event) { > >> > >> LoggerBean row = (LoggerBean) dataTable.getRowData(); > >> String attributeName = row.getLoggerName(); > >> logger.debug("atribute Name:"+attributeName+"|"); > >> } > >> ... > >> } > >> > >> ---LOGGERBEAN--- > >> public class LoggerBean { > >> ... > >> private String loggerName ; > >> > >> } > >> > >> > >> in faces-config.xml, logSort = LogSortHelper > >> > >> > >> > >> Further on , I've tryed to get rid of the component binding stuff... > >> (which > >> in fact I only needed > >> for the dataTable.getRowData() method) . > >> > >> So i did the following modifications : > >> (http://wiki.apache.org/myfaces/ExecutingMethodsFromLinkButtonParameters) > >> > >> ---VIEW--- > >> >> actionListener="#{logSort.modifyLogOnServer4}"> > >> >> value="#{log.loggerName}"/> > >> > >> > >> > >> ---BACKING BEAN--- > >> > >> public String modifyLogOnServer4(javax.faces.event.ActionEvent event) { > >> FacesContext context = FacesContext.getCurrentInstance(); > >> Map map = context.getExternalContext().getRequestParameterMap(); > >> String attributeName = (String) map.get("logDebugId"); > >> } > >> > >> Now I have my actionListener called 30 times... but for the same link( > >> not > >> anymore for all the links > >> in the dataTable, but for the same link... 30 times) > >> > >> > >> And then something else : I am having inconsistent behaviour when > >> changing > >> from commandButton to commandLink... > >> IE : using commandButton my parameter is not passed to the backing > >> bean.(with commandLink I see params > >> in the backing bean) > >> > >> Anybody got any solutions? > >> > >> Regards, > >> Radu Milos > >> > >> > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/CommandLink-in-dataTabl-tf4370964.html#a12458281 > >> 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 > > > > > > -- > View this message in context: > http://www.nabble.com/CommandLink-in-dataTabl
Re: CommandLink in dataTabl
Being stuck with WebLogic 8.1 unfortunatelly means I am stuck with java 1.4 :( this is why I am using sun RI and tomahawk 1.1.1 However, retried again tomahawk 1.1.6 and got an incompatible tld error : /startPage.jsp(3): Could not parse deployment descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache.org/tomahawk' into a valid tag library probably occurred due to an error in /startPage.jsp line 3: <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t" %> mybe some log from the weblogic server could bring some light : weblogic.servlet.jsp.JspException: (line 3): Could not parse deployment descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache .org/tomahawk' into a valid tag library at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:712) at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5067) at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4891) at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4737) at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2147) at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1933) at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1806) at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963) at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106) at weblogic.servlet.jsp.JspParser.parse(JspParser.java:234) at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125) at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258) at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:388) at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:238) at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:188) at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:535) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:373) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:463) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322) at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644) Radu Martin Marinschek wrote: > > what where the problems with these other versions? We should probably > better fix these... > > regards, > > Martin > > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: >> >> First, thanks for the interest. >> Problem is that with WebLogic 8.1(this is my constrain) I am stuck to >> sun >> RI 1.1 and tomahawk 1.1.1 >> I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I >> couldn't get them working. >> >> Radu >> >> >> Martin Marinschek wrote: >> > >> > Hi Radu, >> > >> > you've run into a compatibility problem between Sun RI 1.1 and >> > Tomahawk, both in earlier versions. An upgrade to the latest 1.1 >> > version of both libraries should help! >> > >> > regards, >> > >> > Martin >> > >> > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: >> >> >> >> Hello, >> >> I am a newbie learning JSF while trying to meet deadlines on a JSF >> >> refactoring project. >> >> The docs & forums have helped me quite a lot untill now when I >> seem >> >> to >> >> be facing >> >> a wierd problem. Here is the context : I have a dataTable and a >> >> commandLink >> >> on every >> >> line. The actionListener associated with this commandLink should only >> >> update >> >> some db information >> >> for the concerned record(and then redisplay the same page again). >> >> My problem is that when i click on _one_ link the actionListener is >>
Re: CommandLink in dataTabl
Interesting - it looks as if the tomahawk-tld couldn't be resolved. You might want to try to add the tld into your project directly, and see if this works. regards, Martin On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: > > Being stuck with WebLogic 8.1 unfortunatelly means I am stuck with java 1.4 > :( > this is why I am using sun RI and tomahawk 1.1.1 > However, retried again tomahawk 1.1.6 and got an incompatible tld error : > > /startPage.jsp(3): Could not parse deployment descriptor: > java.io.IOException: cannot resolve 'http://myfaces.apache.org/tomahawk' > into a valid tag library > probably occurred due to an error in /startPage.jsp line 3: > <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t" %> > > > mybe some log from the weblogic server could bring some light : > weblogic.servlet.jsp.JspException: (line 3): Could not parse deployment > descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache > .org/tomahawk' into a valid tag library > at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:712) > at > weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5067) > at > weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4891) > at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4737) > at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2147) > at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1933) > at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1806) > at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963) > at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106) > at weblogic.servlet.jsp.JspParser.parse(JspParser.java:234) > at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125) > at > weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258) > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:388) > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:238) > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:188) > at > weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:535) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:373) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:463) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) > at > weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322) > at > com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322) > at > com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130) > at > com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87) > at > com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) > at > com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) > at > weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) > at > weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718) > at > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) > at > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) > at > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764) > at > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644) > > Radu > > > Martin Marinschek wrote: > > > > what where the problems with these other versions? We should probably > > better fix these... > > > > regards, > > > > Martin > > > > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: > >> > >> First, thanks for the interest. > >> Problem is that with WebLogic 8.1(this is my constrain) I am stuck to > >> sun > >> RI 1.1 and tomahawk 1.1.1 > >> I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I > >> couldn't get them working. > >> > >> Radu > >> > >> > >> Martin Marinschek wrote: > >> > > >> > Hi Radu, > >> > > >> > you've run into a compatibility problem between Sun RI 1.1 and > >> > Tomahawk, both in earlier versions. An upgrade to the latest 1.1 > >> > version of both libraries should help! > >> > > >> > regards, > >> > > >> > Martin > >> > > >> > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: > >> >> > >> >> Hello, > >> >> I am a newbie learning JSF while trying to meet deadlines on a JSF > >> >> refactoring project. > >> >> The docs & forums have hel
Re: CommandLink in dataTabl
Finally i reconsidered the compatibility issue, spent some more time on it and got working toghether(like a miracle) the following : WebLogic 8.1 SP4, myfaces 1.5 and tomahawk 1.1.6 !! Martin Marinschek wrote: > > Interesting - it looks as if the tomahawk-tld couldn't be resolved. > You might want to try to add the tld into your project directly, and > see if this works. > > regards, > > Martin > > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: >> >> Being stuck with WebLogic 8.1 unfortunatelly means I am stuck with java >> 1.4 >> :( >> this is why I am using sun RI and tomahawk 1.1.1 >> However, retried again tomahawk 1.1.6 and got an incompatible tld error : >> >> /startPage.jsp(3): Could not parse deployment descriptor: >> java.io.IOException: cannot resolve 'http://myfaces.apache.org/tomahawk' >> into a valid tag library >> probably occurred due to an error in /startPage.jsp line 3: >> <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t" %> >> >> >> mybe some log from the weblogic server could bring some light : >> weblogic.servlet.jsp.JspException: (line 3): Could not parse deployment >> descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache >> .org/tomahawk' into a valid tag library >> at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:712) >> at >> weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5067) >> at >> weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4891) >> at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4737) >> at >> weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2147) >> at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1933) >> at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1806) >> at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963) >> at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106) >> at weblogic.servlet.jsp.JspParser.parse(JspParser.java:234) >> at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125) >> at >> weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258) >> at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:388) >> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:238) >> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:188) >> at >> weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:535) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:373) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:463) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) >> at >> weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322) >> at >> com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322) >> at >> com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130) >> at >> com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87) >> at >> com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) >> at >> com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117) >> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) >> at >> weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) >> at >> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718) >> at >> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) >> at >> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) >> at >> weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764) >> at >> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644) >> >> Radu >> >> >> Martin Marinschek wrote: >> > >> > what where the problems with these other versions? We should probably >> > better fix these... >> > >> > regards, >> > >> > Martin >> > >> > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: >> >> >> >> First, thanks for the interest. >> >> Problem is that with WebLogic 8.1(this is my constrain) I am stuck to >> >> sun >> >> RI 1.1 and tomahawk 1.1.1 >> >> I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I >> >> couldn't get them working. >> >> >> >> Radu >> >> >> >> >> >> Martin Marinschek wrote: >> >> > >> >> > Hi Radu, >> >> > >> >> > you've run into a compatibility problem between Sun RI 1.1 and >> >> > Tomahawk, both in earlier versio
Re: CommandLink in dataTabl
I looked at the HTML generated code and I noticed that each button had the same HTML code... there were no unique ID's. I believe this is the reason why my method got called hundreds of times... Maybe there could be some issue in generating the ids. However, I moved to myfaces 1.5 and tomahawk 1.1.6 and stumbled over other bugs :) Thanks for the support! Martin Marinschek wrote: > > Interesting - it looks as if the tomahawk-tld couldn't be resolved. > You might want to try to add the tld into your project directly, and > see if this works. > > regards, > > Martin > > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: >> >> Being stuck with WebLogic 8.1 unfortunatelly means I am stuck with java >> 1.4 >> :( >> this is why I am using sun RI and tomahawk 1.1.1 >> However, retried again tomahawk 1.1.6 and got an incompatible tld error : >> >> /startPage.jsp(3): Could not parse deployment descriptor: >> java.io.IOException: cannot resolve 'http://myfaces.apache.org/tomahawk' >> into a valid tag library >> probably occurred due to an error in /startPage.jsp line 3: >> <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t" %> >> >> >> mybe some log from the weblogic server could bring some light : >> weblogic.servlet.jsp.JspException: (line 3): Could not parse deployment >> descriptor: java.io.IOException: cannot resolve 'http://myfaces.apache >> .org/tomahawk' into a valid tag library >> at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:712) >> at >> weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5067) >> at >> weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4891) >> at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4737) >> at >> weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2147) >> at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1933) >> at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1806) >> at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963) >> at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106) >> at weblogic.servlet.jsp.JspParser.parse(JspParser.java:234) >> at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125) >> at >> weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258) >> at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:388) >> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:238) >> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:188) >> at >> weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:535) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:373) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:463) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) >> at >> weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322) >> at >> com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322) >> at >> com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130) >> at >> com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87) >> at >> com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) >> at >> com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117) >> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) >> at >> weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419) >> at >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) >> at >> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718) >> at >> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) >> at >> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) >> at >> weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764) >> at >> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644) >> >> Radu >> >> >> Martin Marinschek wrote: >> > >> > what where the problems with these other versions? We should probably >> > better fix these... >> > >> > regards, >> > >> > Martin >> > >> > On 9/3/07, radu_milos <[EMAIL PROTECTED]> wrote: >> >> >> >> First, thanks for the interest. >> >> Problem is that with WebLogic 8.1(this is my constrain) I am stuck to >> >> sun >> >> RI 1.1 and tomahawk 1.1.1 >> >> I've tryed the other versions of tomahawk (from 1.1.2 to 1.1.6) and I >> >> couldn't get them working. >> >> >> >> Radu >> >> >> >> >>