Why don't you just grab the latest Workbench code (that includes a ShowMessages sample component) and work your way out from there? I always find that it's better to start with working code first and then branch out..
http://people.apache.org/repo/m2-snapshot-repository/org/apache/tapestry/tapestry-Workbench/4.1.1-SNAPSHOT/tapestry-Workbench-4.1.1-20061017.225719-37.war On 10/17/06, James Carman <[EMAIL PROTECTED]> wrote:
The class="proto.component.ShowMessages" part of your component specification (ShowMessages.jwc) says that there has to be a class called proto.component.ShowMessages. -----Original Message----- From: Ken nashua [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 1:56 PM To: users@tapestry.apache.org Subject: RE Component ApplicationRuntimeException... Tap-4.1.1 help please (thanks) Dude..., There is no such class file for these components. I scooped them up from http://files.doublenegative.com.au/jumpstart/download.html And it seems HLS stamped his name on them too. No java files included in the war at http://files.doublenegative.com.au/jumpstart/download.html Are you implying that tapestry should pre-compile these during build and package? Do such java files exist? Should they? Or does tapestry generate them at runtime? ---> Here is the actual ShowMessages.html <span jwcid="$content$"> <span jwcid="@If" condition="ognl:page.beans.validationDelegate.hasErrors"> <span jwcid="@ShowError">--- Validation error message ---</span> </span> <span jwcid="@If" condition="ognl:page.warningMessage"> <span jwcid="@Insert" value="ognl:page.warningMessage" class="warning">--- Warning message ---</span> </span> <span jwcid="@If" condition="ognl:page.infoMessage"> <span jwcid="@Insert" value="ognl:page.infoMessage" class="info">--- Info message ---</span> </span> </span> ---> Here is the actual ShowMessages.jwc <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE component-specification PUBLIC "-//Apache Software Foundation//Tapestry Specification 4.0//EN" "http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd";> <component-specification class="proto.component.ShowMessages" allow-body="no" allow-informal-parameters="no"> </component-specification> How do you arrive at I need *.class files for this when there are no java files? Should there be java files for this component? Anyhow... I still receive the namespace exception... even after I tore the components out and pre-built/deployed them from within their own private proto.component maven project as a proto.component-1.0.jar which is a custom component deliverable... kinda like contrib. I look forward to your feedback. - cheers Ken -- Here is the new application file <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application PUBLIC "-//Apache Software Foundation//Tapestry Specification 4.0//EN" "http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd";> <!-- generated by Spindle, http://spindle.sourceforge.net --> <DEFANGED_application name="tap.proto"> <DEFANGED_meta key="org.apache.tapestry.page-class-packages" value="proto"/> <DEFANGED_meta key="org.apache.tapestry.component-class-packages" value="proto.component"/> <library id="trails" specification-path="/org/trails/component/trails.library"/> <library id="contrib" specification-path="/org/apache/tapestry/contrib/Contrib.library"/> <library id="tacos" specification-path="/net/sf/tacos/Tacos.library"/> <library id="proto.component" specification-path="/proto/component/proto.component.library"/> </application> ---> Here is the new library file from the private component project <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application PUBLIC "-//Apache Software Foundation//Tapestry Specification 4.0 //EN" "http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd";> <!-- generated by Spindle, http://spindle.sourceforge.net --> <library-specification> <description>Prototype Component library</description> <DEFANGED_meta key="org.apache.tapestry.component-class-packages" value="proto.component"/> <library id="trails" specification-path="/org/trails/component/trails.library"/> <library id="contrib" specification-path="/org/apache/tapestry/contrib/Contrib.library"/> <library id="tacos" specification-path="/net/sf/tacos/Tacos.library"/> <component-type type="ShowError" specification-path="ShowError.jwc"/> <component-type type="ShowMessages" specification-path="ShowMessages.jwc"/> </library-specification> Everything is aligned pathwise within each jar/war --------------------------------------------------------------------- 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]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
