4.0 application config <property>

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

4.0 application config <property>

Gregg D Bolinger
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Gregg D Bolinger
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 <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Gregg D Bolinger
Ok, so it looks like the visit-class now has to be configured in the
HiveMind deployment descriptor.  Is this correct?

On 5/9/05, Gregg D Bolinger <[hidden email]> 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 <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Jamie Orchard-Hays
In reply to this post by Gregg D Bolinger
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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Gregg D Bolinger
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 <[hidden email]> 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 <[hidden email]> 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: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Howard Lewis Ship
Gregg,

I appreciate that you're steaming ahead into unchartered 4.0 alpha
territories, but ...

http://jakarta.apache.org/tapestry/current/UsersGuide/upgrade.html

There is documentation to describe exactly what's changed.

On 5/9/05, Gregg D Bolinger <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Howard Lewis Ship
Going too fast for me own good ...

http://jakarta.apache.org/tapestry/current/UsersGuide/spec.html#spec.changes

is the specific details about renames and changes in the DTDs.  The other URL

http://jakarta.apache.org/tapestry/current/UsersGuide/upgrade.html

Covers the wider view (i.e., what to change in your Java file).


On 5/9/05, Howard Lewis Ship <[hidden email]> wrote:

> Gregg,
>
> I appreciate that you're steaming ahead into unchartered 4.0 alpha
> territories, but ...
>
> http://jakarta.apache.org/tapestry/current/UsersGuide/upgrade.html
>
> There is documentation to describe exactly what's changed.
>
> On 5/9/05, Gregg D Bolinger <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com
>


--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Jamie Orchard-Hays
In reply to this post by Gregg D Bolinger
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 <[hidden email]> 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 <[hidden email]> 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: [hidden email]
>>>For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail: [hidden email]
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Gregg D Bolinger
In reply to this post by Howard Lewis Ship
Somehow this just went to howard the last time.

GREAT!  Thanks.  I'm sure that will get just what I need.

Gregg

On 5/9/05, Howard Lewis Ship <[hidden email]> wrote:

> Going too fast for me own good ...
>
> http://jakarta.apache.org/tapestry/current/UsersGuide/spec.html#spec.changes
>
> is the specific details about renames and changes in the DTDs.  The other URL
>
> http://jakarta.apache.org/tapestry/current/UsersGuide/upgrade.html
>
> Covers the wider view (i.e., what to change in your Java file).
>
>
> On 5/9/05, Howard Lewis Ship <[hidden email]> wrote:
> > Gregg,
> >
> > I appreciate that you're steaming ahead into unchartered 4.0 alpha
> > territories, but ...
> >
> > http://jakarta.apache.org/tapestry/current/UsersGuide/upgrade.html
> >
> > There is documentation to describe exactly what's changed.
> >
> > On 5/9/05, Gregg D Bolinger <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> > --
> > Howard M. Lewis Ship
> > Independent J2EE / Open-Source Java Consultant
> > Creator, Jakarta Tapestry
> > Creator, Jakarta HiveMind
> >
> > Professional Tapestry training, mentoring, support
> > and project work.  http://howardlewisship.com
> >
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Erik Hatcher
In reply to this post by Jamie Orchard-Hays
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 <[hidden email]> 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 <[hidden email]> 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-
>>>> [hidden email]
>>>> For additional commands, e-mail: tapestry-user-
>>>> [hidden email]
>>>>
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: tapestry-user-
>>> [hidden email]
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: tapestry-user-
>> [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 4.0 application config <property>

Gregg D Bolinger
COOL!  Thanks Erik.  That helped A LOT!

Gregg

On 5/9/05, Erik Hatcher <[hidden email]> wrote:

> 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 <[hidden email]> 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 <[hidden email]> 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-
> >>>> [hidden email]
> >>>> For additional commands, e-mail: tapestry-user-
> >>>> [hidden email]
> >>>>
> >>>>
> >>>>
> >>>
> >>> --------------------------------------------------------------------
> >>> -
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: tapestry-user-
> >>> [hidden email]
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: tapestry-user-
> >> [hidden email]
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]