[EMAIL PROTECTED]: Project struts-core (in module struts) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project struts-core has an issue affecting its community integration. This issue affects 5 projects, and has been outstanding for 21 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - fulcrum-quartz : Services Framework - jakarta-turbine-jcs : Cache - quartz : Job Scheduler - struts-core : Model 2 Model-View-Controller framework for Servlets and JSP - struts-tiles : Model 2 Model-View-Controller framework for Servlets and JSP Full details are available at: http://vmgump.apache.org/gump/public/struts/struts-core/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [struts.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property xerces.jar. -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/struts/struts-core/gump_work/build_struts_struts-core.html Work Name: build_struts_struts-core (Type: Build) Work ended in a state of : Failed Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dcommons-beanutils.jar=/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar -Djakarta-oro.jar=/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-19082005.jar -Dcommons-chain.jar=/usr/local/gump/public/workspace/jakarta-commons/chain/target/commons-chain-19082005.jar -Dantlr.jar=/usr/local/gump/packages/antlr-2.7.3/antlr.jar -Djdbc20ext.jar=/usr/local/gump/packages/jdbc2_0/jdbc2_0-stdext.jar -Dcommons-lang.jar=/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-19082005.jar -Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-19082005.jar -Djdk.version=1.4 -Dservlet.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar -Dcommons-validator.jar=/usr/local/gump/public/workspace/jakarta-commons/validator/dist/commons-validator.jar -Dcommons-digester-rss.jar=/usr/local/gump/public/workspace/jakarta-commons/digester/src/examples/rss/dist/commons-digester-rss.jar -Dxerces.jar=/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar -Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-19082005.jar -Dcommons-fileupload.jar=/usr/local/gump/public/workspace/jakarta-commons/fileupload/target/commons-fileupload-19082005.jar -Dcommons-digester.jar=/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar dist [Working Directory: /usr/local/gump/public/workspace/struts/core] CLASSPATH:
RE: [shale][clay] Updating clay config file on the fly
From: Gary VanMatre said: I was poking around in log4j and found a very similar feature that allows you to configure a file watch dog for the properties files. You can't use that within a J2EE container, however, because it spawns a watcher thread. This thread is then outside the lifecycle control of the container. - George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [shale][clay] Updating clay config file on the fly
From: Gary VanMatre said: I was poking around in log4j and found a very similar feature that allows you to configure a file watch dog for the properties files. You can't use that within a J2EE container, however, because it spawns a watcher thread. This thread is then outside the lifecycle control of the container. I believe that you can spawn threads in a J2EE web container. The restriction is only within the EJB container. I'm not sure if there are limitations in a portal but a client or applet J2EE container doesn't have thread restrictions. Shale doesn't support portals yet. Gary - George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 36223] - html:form does not generate a name attribute when in XHTML
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36223. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36223 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2005-08-19 16:41 --- *** This bug has been marked as a duplicate of 35127 *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35127] - [taglib] All Javascript validation fails when html:xhtml/ is present
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35127. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35127 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2005-08-19 16:41 --- *** Bug 36223 has been marked as a duplicate of this bug. *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [shale][clay] Updating clay config file on the fly
From: Gary VanMatre [EMAIL PROTECTED] I believe that you can spawn threads in a J2EE web container. The restriction is only within the EJB container. I'm not sure if there are limitations in a portal but a client or applet J2EE container doesn't have thread restrictions. Shale doesn't support portals yet. SRV.1.2 of the Servlet 2.4 spec says that a servlet container may place security restrictions on the environment in which a servlet executes. It then gives the example, high-end application servers may limit the creation of a Thread object to insure that other components of the container are not negatively impacted. -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [shale][clay] Updating clay config file on the fly
From: Gary VanMatre [EMAIL PROTECTED] I believe that you can spawn threads in a J2EE web container. The restriction is only within the EJB container. I'm not sure if there are limitations in a portal but a client or applet J2EE container doesn't have thread restrictions. Shale doesn't support portals yet. SRV.1.2 of the Servlet 2.4 spec says that a servlet container may place security restrictions on the environment in which a servlet executes. It then gives the example, high-end application servers may limit the creation of a Thread object to insure that other components of the container are not negatively impacted. Ahh, from the writ, good to know. Thanks Wendy. Gary -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Struts Wiki] Update of StrutsBook by Vic Cekvenich
Dear Wiki user, You have subscribed to a wiki page or wiki category on Struts Wiki for change notification. The following page has been changed by Vic Cekvenich: http://wiki.apache.org/struts/StrutsBook New page: This book is current to 1.27, and I hope other jump in and update it to 1.3. It's know for http://infonoia.com/en/content.jsp?d=inf.04.01 among other things. Best use is for somone teaching Struts to use this, as it has labs. I used to teach this in 30 hours 90% lab time to large groups for good rates. It's avilable hardcopy in Fr and Gr. (How do I attach, upload? .V) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Struts Wiki] Update of StrutsBook by Vic Cekvenich
Dear Wiki user, You have subscribed to a wiki page or wiki category on Struts Wiki for change notification. The following page has been changed by Vic Cekvenich: http://wiki.apache.org/struts/StrutsBook -- It's know for http://infonoia.com/en/content.jsp?d=inf.04.01 among other things. Best use is for somone teaching Struts to use this, as it has labs. I used to teach this in 30 hours 90% lab time to large groups for good rates. It's avilable hardcopy in Fr and Gr. - (How do I attach, upload? .V) + You have to click actions/attachments at bottom to download. (you can then edit, and upload so others benefit). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 36276] New: - Struts Tag html:messages/ sets message to null when iterating 2nd time
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36276.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36276
Summary: Struts Tag html:messages/ sets message to null when
iterating 2nd time
Product: Struts
Version: 1.2.7
Platform: Other
OS/Version: other
Status: NEW
Severity: critical
Priority: P2
Component: Custom Tags
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]
Struts Tag html:messages/ sets current message to null if the message type
resource is set to false.
This results in an exception when the JSP is evaluated: bean:write/ doesn't
find the bean in expected page scope.
I found the error in the code of the implementing tag class.
class: org.apache.struts.taglib.html.MessagesTag
CVS Id: $Id: MessagesTag.java 164530 2005-04-25 03:11:07Z niallp $
release: Struts 1.2.7
erroneous code (lines 253..260):
ActionMessage report = (ActionMessage) iterator.next();
String msg =
TagUtils.getInstance().message(
pageContext,
bundle,
locale,
report.getKey(),
report.getValues());
should be replaced by:
ActionMessage report = (ActionMessage) this.iterator.next();
String msg = null;
if (report.isResource()) {
msg = TagUtils.getInstance().message(
pageContext,
bundle,
locale,
report.getKey(),
report.getValues());
} else {
msg = report.getKey();
}
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Struts Wiki] Update of StrutsWebsiteConversion by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Struts Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsWebsiteConversion -- * [DONE] Change links in all navigation.xml files under 'site' to be relative to the root directory * [DONE] Add the missing body tags to navigation.xml files * [DONE] Change the anchors in navigation.xml files to match the section names - * Add navigation.xml files to xdocs under each subproject + * [DONE]Add navigation.xml files to xdocs under each subproject - * Remove the search section from userGuide/index.xml and faqs/index.xml + * [DONE]Remove the search section from userGuide/index.xml and faqs/index.xml + * Remove 'href' attributes from section and subsection tags, add a name='...'/ to preserve existing anchors + * Add a page with links to JavaDoc for each subproject. * User Guide * Fix links to Taglib Package Descriptions (JavaDoc) in the User Guide + * Fix links to Taglib API References in the User Guide - * Change chapter and section to section and subsection + * [DONE] Change chapter and section to section and subsection - * Change pre code blocks to source + * [DONE] Change pre code blocks to source + * [DONE] Generate and link in the TLD documentation + * Maven Taglib Plugin: http://maven-taglib.sourceforge.net/ === Post-Conversion To Do List === - * Generate TLD documentation and fix links to Taglib API References in the User Guide - * Maven Taglib Plugin: http://maven-taglib.sourceforge.net/ * Move relevant documentation down to the sub-project level * Generate HTML and PDF versions of the documentation * Maven PDF plugin: http://maven.apache.org/reference/plugins/pdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
http://struts.apache.org/mail.html
Bottom of the page links to proj.com. Can somone please change it to: http://struts_user.roomity.com (I takes you into the struts mail list). tia, .V - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [shale][clay] Updating clay config file on the fly
On 8/18/05, Gary VanMatre [EMAIL PROTECTED] wrote: On 7/28/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Now that would be cool. I think we would have to load all clay config files to resolve the inheritance dependencies but that would be way slick. Yep, you'd need to reload the whole set. Plus, do it in a way that does not require you to have sync locks on all the *uses* of the old configuration data while the new stuff is being parsed. For production deployment, it's likely that we would want the reload capability disabled (most of the IT guys I know would laugh me out of the room if I proposed to fix a typo in a running JSP page, on a live production app :-). Indeed, disabled should probably be the default, so that you can turn it on for development via a context parameter or something. I was poking around in log4j and found a very similar feature that allows you to configure a file watch dog for the properties files. It would be pretty simple to extend the abstract org.apache.log4j.helpers.FileWatchdog implementation. We don't have a dependency with log4j in Shale. Besides the issues on creating threads (which could be handled differently -- say with a Filter -- in environments where they were disallowed), it's not clear to me that a solution focused solely on files is the right one. Yes, that is a very common use case, but I'd rather see the concept implemented based on using the URL APIs to detect the last modified time. The input would be the URL returned by ServletContext.getResourceURL(), and you would thus be able to operate on servlet containers that, say, stored some of their static content in a database instead of in the filesystem. Craig Would it be possible to copy in the one class leaving the original Copyright? I know that we have a similar discussion regarding Clay and Tapestry but I didn't have the courage to ask. Gary Gary Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
