3.0 -> 4.0:
<property-specification> -> <property>
<property> -> <meta>And, no, you don't need a HiveMind (hivemodule.xml) file to declare a visit. Here's the .application file for the current app I'm building:
<?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";>
<application name="collex" engine- class="org.patacriticism.collex.CollexEngine" >
<meta key="org.apache.tapestry.global-class" value="org.patacriticism.collex.Global"/>
<meta key="org.apache.tapestry.visit-class" value="org.patacriticism.collex.Visit"/>
<meta key="org.apache.tapestry.default-page-class" value="org.patacriticism.collex.SecuredPage"/>
<extension name="org.apache.tapestry.monitor-factory" class="org.patacriticism.collex.CollexMonitorFactory"/>
<library id="contrib" specification-path="/org/apache/tapestry/ contrib/Contrib.library"/>
</application>
Only the <meta> stuff is different, which used to be <property>.
Erik
On May 9, 2005, at 3:46 PM, Jamie wrote:
I'm not yet working with Picasso, but perhaps Erik and Howard will chime in here.
Jamie
Gregg D Bolinger wrote:
Yeah, I do see the new attributes. But they don't make sense anymore.
Example....
3.0 way:
<property-specification name="password" type="java.lang.String"
persistent="no"/>
4.0 way?
<property name="password" initial-value="" persist="no"/>
I can only assume that initial-value is optional and I don't have to
specify the type anymore?
I would test it but I can't even get a simple hello app to work yet
because I don't have a clear line of site on what all JAR's are needed
now beyond the hivemind jars and the latest is I get an exception that
it can't find the 4.0 DTD when parsing the .page files. Yes, I know I
could still just use 3.0 but I'd like to help Howard et al by testing
all the 4.0 specifics.
Gregg
On 5/9/05, Jamie <[EMAIL PROTECTED]> wrote:
Gregg, if you're pointing at the new 4.0 DTD and you've got completion,---------------------------------------------------------------------
then you should be able to see the new valid attributes. Otherwise, have
a look into the DTD itself to get a quick overview of the changes to the
elements and attributes.
Gregg D Bolinger wrote:
Looks like things have changed in the .page files as well.
<property-specification> is no longer valid. I looked at <property>
but then type and persisistent attributes are not valid. What is used
now? Are .page files still needed at all?
Gregg
On 5/9/05, Gregg D Bolinger <[EMAIL PROTECTED]> wrote:
The <property> element appears to no longer be valid in the
.application file. I was using it to specify my own Visit class. Is
there an element that has replaced this or it is done differently now.
Gregg Bolinger
------------------------------------------------------------------- --
To unsubscribe, e-mail: tapestry-user- [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user- [EMAIL PROTECTED]
-------------------------------------------------------------------- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user- [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user- [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]
