Re: please maven clean continuum [was: [continuum] BUILD FAILURE: Myfaces Nighly Build Script]
Hey boy, Bernd changed the pom xml yea - tx a lot for this, however, I do not understand why my and others local build worked without this change - however a tree times salut to Bernd. Ciao, Mario
[jira] Created: (TOBAGO-86) resource dirs needs defined order
resource dirs needs defined order - Key: TOBAGO-86 URL: http://issues.apache.org/jira/browse/TOBAGO-86 Project: MyFaces Tobago Type: Bug Reporter: Volker Weber Assigned to: Volker Weber Fix For: 1.0.8 Attachments: TobagoConfig.diff tobago resource lookup needs a defined order, which is not guaranteed from currendly used HashSet -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOBAGO-86) resource dirs needs defined order
[ http://issues.apache.org/jira/browse/TOBAGO-86?page=all ] Volker Weber updated TOBAGO-86: --- Status: Patch Available (was: Open) resource dirs needs defined order - Key: TOBAGO-86 URL: http://issues.apache.org/jira/browse/TOBAGO-86 Project: MyFaces Tobago Type: Bug Reporter: Volker Weber Assignee: Volker Weber Fix For: 1.0.8 Attachments: TobagoConfig.diff tobago resource lookup needs a defined order, which is not guaranteed from currendly used HashSet -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOBAGO-87) NPE when decoding PageState without state value in request
NPE when decoding PageState without state value in request -- Key: TOBAGO-87 URL: http://issues.apache.org/jira/browse/TOBAGO-87 Project: MyFaces Tobago Type: Bug Reporter: Volker Weber Assigned to: Volker Weber -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOBAGO-87) NPE when decoding PageState without state value in request
[ http://issues.apache.org/jira/browse/TOBAGO-87?page=all ] Volker Weber updated TOBAGO-87: --- Status: Patch Available (was: Open) NPE when decoding PageState without state value in request -- Key: TOBAGO-87 URL: http://issues.apache.org/jira/browse/TOBAGO-87 Project: MyFaces Tobago Type: Bug Reporter: Volker Weber Assignee: Volker Weber Attachments: UIPage.diff -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOBAGO-88) Warning page contains secure and nonsecure items on IE when using https
Warning page contains secure and nonsecure items on IE when using https --- Key: TOBAGO-88 URL: http://issues.apache.org/jira/browse/TOBAGO-88 Project: MyFaces Tobago Type: Bug Environment: IE and https application Reporter: Volker Weber Assigned to: Volker Weber -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOBAGO-88) Warning page contains secure and nonsecure items on IE when using https
[ http://issues.apache.org/jira/browse/TOBAGO-88?page=all ] Volker Weber updated TOBAGO-88: --- Status: Patch Available (was: Open) Warning page contains secure and nonsecure items on IE when using https --- Key: TOBAGO-88 URL: http://issues.apache.org/jira/browse/TOBAGO-88 Project: MyFaces Tobago Type: Bug Environment: IE and https application Reporter: Volker Weber Assignee: Volker Weber Attachments: iframes.diff -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Displaying radio buttons in datatable
I tried using SelectOneRow Component in tomahawk sandbox but faces problems with jar files. I need to use t:selectOneRadio or h:selectOneRadio component. When i removed the forceId and forceIndexId i was able to do mutiple selections whicxh is against my requirement. I am restricted using javascript. Is there any way to get rid of this issue. -- View this message in context: http://www.nabble.com/Displaying-radio-buttons-in-datatable-tf1861637.html#a507 Sent from the My Faces - Dev forum at Nabble.com.
Source attachment jars for MyFaces and Tomahawk
Hi, During the development of my JSF projects and components, I often like to step into the (JSF) framework code during debugging. As I'm using MyFaces and Tomahawk 1.1.3, I was looking for a source code jar (or tar) for these. http://apache.org/dev/version-control.html tells me to look up the distribution directory. I did so, but there is no source code for the current release there. I checked multiple mirrors, but the latest source they contain is for 1.1.1 from October 2005. I then tried to retrieve the code from the SVN repository to build my own jar for source attachment. However, I run into some problems with the shared packages (shared_imp shared_tomahawk). These have a different branch tag in the SVN repository (2_0_3, 3_0_0 instead of 1_1_2, 1_1_3, etc). I'm not sure which version(s) of shared the binary distributions are using. On top of that, I have to generate impl and tomahawk versions before I can copy them to the respective source packages I'm building. So, I wonder whether there are any source attachment jars just ready for downloading somewhere? It would be even greater if the source jars could be bundled with the main distribution (since these also contain the javadoc jars, it shouldn't be that much trouble to also include the source), but I realize that may be too much to ask ;) Kind regards, Arjan Tijms
[jira] Created: (MYFACES-1346) exception when using a custom error page and a 404 occurs with an address that matches pattern for FasesServlet
exception when using a custom error page and a 404 occurs with an address that matches pattern for FasesServlet --- Key: MYFACES-1346 URL: http://issues.apache.org/jira/browse/MYFACES-1346 Project: MyFaces Core Type: Bug Versions: 1.1.3, 1.1.1 Environment: JBoss-3.2.7 Reporter: Michal Borowiecki I have defined a custom error page and mapped it (among others) to 404 errors in web.xml: error-page error-code400/error-code location/error.jspx/location /error-page It works for all addresses except those that match the mapping for the FacesServlet (*.jsf). When a page that doesn't exist is requested, a standard Tomcat error page is shown instead of the custom error page and the following exception is logged: 2006-06-29 12:50:32,655 ERROR TP-Processor6 [Engine] ApplicationDispatcher[] Servlet.service() for servlet jsp threw exception java.lang.IllegalStateException: getOutputStream() has already been called for this response at org.apache.coyote.tomcat5.CoyoteResponse.getWriter(CoyoteResponse.java:600) at org.apache.coyote.tomcat5.CoyoteResponseFacade.getWriter(CoyoteResponseFacade.java:164) at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:124) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:117) at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:191) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:115) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:75) at org.apache.jsp.error_jspx._jspService(error_jspx.java:185) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:696) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:476) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:396) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:301) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:147) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:534) 2006-06-29 12:50:32,657 ERROR TP-Processor6 [Engine] [EMAIL PROTECTED]: Exception Processing ErrorPage[errorCode=404, location=/error.jspx] java.lang.IllegalStateException: getOutputStream() has already been called for
[jira] Resolved: (MYFACES-612) IllegalStateException: Cannot forward after response has been committed
[ http://issues.apache.org/jira/browse/MYFACES-612?page=all ]
Jeremy Green resolved MYFACES-612:
--
Resolution: Invalid
This seems to be an issue with Tomcat / Java 2D, and not MyFaces:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6326655
http://issues.apache.org/bugzilla/show_bug.cgi?id=37516
Sun's Application servers and Jetty don't seem to have the same problem.
IllegalStateException: Cannot forward after response has been committed
---
Key: MYFACES-612
URL: http://issues.apache.org/jira/browse/MYFACES-612
Project: MyFaces Core
Type: Bug
Components: General
Versions: 1.1.0
Environment: Tomcat 5.5.7, Sun JDK 1.5.0, Mozilla 1.7.10 and Linux.
Reporter: Jeremy Green
Assignee: Manfred Geiler
Rapid, multiple clicks on the h:commandButton in the test case given below
produce an IllegalStateException and a blank response about 10% of the time.
The JSF state-saving method can be client or server. A blank page is sometimes
returned even if the clicks are not rapid.
The Sun JSF RI 1.1_01 shows the same problem:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6326655
The stack trace is:
SEVERE: Servlet.service() for servlet Faces Servlet threw exception
java.lang.IllegalStateException: Cannot forward after response has been
committed
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:314)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
at
org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:415)
at
org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234)
at
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:300)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:95)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:362)
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:214)
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:825)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
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:595)
Here is the test case:
index.jsp:
%@ taglib uri=http://java.sun.com/jsf/html; prefix=h %
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
html
head/head
body
f:view
h:form
p
h:commandButton value=Submit /
/p
p
h:graphicImage value=image.png /
/p
/h:form
/f:view
/body
/html
SlowServlet.java, mapped to image.png in web.xml:
public class SlowServlet extends HttpServlet {
protected void doGet(HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException {
BufferedImage image;
OutputStream os;
image = new BufferedImage(100, 100,
BufferedImage.TYPE_INT_ARGB);
os = resp.getOutputStream();
resp.setContentType(image/png);
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
throw new ServletException(e);
}
try {
ImageIO.write(image, png, os);
os.close();
} catch (IOException e) {
}
}
}
--
This message is automatically generated by JIRA.
-
If you
Re: Problems building myfaces
On 6/28/06, Cosma Colanicchia [EMAIL PROTECTED] wrote: I have done a fresh checkout of latest myfaces, and just installed maven 2.0.4. I cant build myfaces, mvn install gives me this error: ... Reason: Unable to download the artifact from any repository org.apache.myfaces.maven:myfaces-master:pom:1.0.5-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) What instructions are you following (so that we can update them if necessary)? lI assume you have checked out: svn co http://svn.apache.org/repos/asf/myfaces/current myfaces From that top-level directory, 'mvn install' works fine for me -- the first thing it does is install the myfaces-master pom that your build claims is missing. If you're still having trouble, please post the exact commands you are typing so we can help you figure out what's wrong. Thanks! -- Wendy
Re: Problems building myfaces
I followed the instructions on http://wiki.apache.org/myfaces/Building_With_Maven.. or at least I think so :) I'm having a look at the stuff svn downloaded and I see only the site folder inside of src! Probably I mispelled the url (it was late...) I'm checking it out again and it seems that the real sources are now being downloaded.. thank you Wendy. Cosma 2006/6/29, Wendy Smoak [EMAIL PROTECTED]: On 6/28/06, Cosma Colanicchia [EMAIL PROTECTED] wrote: I have done a fresh checkout of latest myfaces, and just installed maven 2.0.4. I cant build myfaces, mvn install gives me this error: ... Reason: Unable to download the artifact from any repository org.apache.myfaces.maven:myfaces-master:pom:1.0.5-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) What instructions are you following (so that we can update them if necessary)? lI assume you have checked out: svn co http://svn.apache.org/repos/asf/myfaces/current myfaces From that top-level directory, 'mvn install' works fine for me -- the first thing it does is install the myfaces-master pom that your build claims is missing. If you're still having trouble, please post the exact commands you are typing so we can help you figure out what's wrong. Thanks! -- Wendy
[job] Remote MyFaces developper job offer
Hello MyFaces developers, We have a job offer opening for one or two good JSF developers, and some of you might be interested. Here is the offer : Full time remote job with some meetings (once or twice a year in either Paris - France or Dubai - UAE). Goal : Participate in the development of the new Freelance.com's intranet web. Main tools : Java 1.5, Maven, MyFaces, Hibernate, Tomcat. The developer must be in a time zone compatible with the UAE (GMT+4). That is either Europe, Africa, Middle East or Asia, but not America or Australia. He must be fluent in English or French. If you are interested, please send me your resume and your price at [EMAIL PROTECTED] Thank you, Sylvain Vieujot CEO / CIO Freelance.com
[jira] Created: (TOMAHAWK-509) t:saveState does not check to see if the value attribute implements StateHolder.
t:saveState does not check to see if the value attribute implements StateHolder. Key: TOMAHAWK-509 URL: http://issues.apache.org/jira/browse/TOMAHAWK-509 Project: MyFaces Tomahawk Type: Improvement Reporter: Matt Hughes The JavaDocs for t:saveState say (http://myfaces.apache.org/tomahawk/apidocs/org/apache/myfaces/custom/savestate/UISaveState.html ): --- The object being saved must either: * implement java.io.Serializable, or * implement javax.faces.component.StateHolder and have a default constructor. However, the component does nothing if the object implements StateHolder. If the object being saved does implement StateHolder and does not implement Serializable, the component should use the StateHolder mechanism of saveState()/restoreState(). This allows the object to determine what properties it actually wants to have saved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Tomahawk Maven2 oddity: 1.1.3 requires Shale and Struts1.2.8. Why?
On 6/29/06, David Friedman [EMAIL PROTECTED] wrote: And it suddenly added Struts-1.2.8 to my .war file. The tomahawk-1.1.3.pom file lists Struts like so: dependency groupIdstruts/groupId artifactIdstruts/artifactId version1.2.8/version scopecompile/scope /dependency What kind of dependency is that? I couldn't find anything in the Wiki about it as some kind of Tomahawk 1.1.3 upgrade dependencies. I can understand Shale for the test segment but it is ALSO getting packaged by Maven2 in my .war file: Maven should not be picking up a 'test' scoped dependency in your .war file. I think the Struts dependency is wrong -- it should be marked 'optional'. You can add an exclusion to the tomahawk dependency in your pom to get rid of it. I'm going to move this to the dev list because we've branched for 1.1.4 and we'll need to check this on both the branch and the trunk. Can someone please check and/or open a JIRA issue for it? Followups on dev@myfaces.apache.org, please. -- Wendy
