You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Phil Zoio <ph...@realsolve.co.uk> on 2005/06/29 23:23:57 UTC

Tapestry 4 - can we get rid of the .page files?

With annotation support it seems like it will be possible soon to get 
rid of the .page and .jwc altogether.

Right now with annotations I'm down to only one piece of information in 
my .page and .jwc classes - the name of the class itself. Is there any 
way to configure this without using a page or jwc class?

Regards,
Phil Zoio

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Tapestry 4 - can we get rid of the .page files?

Posted by Phil Zoio <ph...@realsolve.co.uk>.
I've tried this and coming up with exception:

Page 'Home' not found in application namespace.
Stack Trace:

    * org.apache.tapestry.resolver.PageSpecificationResolverImpl.resolve(PageSpecificationResolverImpl.java:140)

    * $PageSpecificationResolver_104cdb0f1c9.resolve($PageSpecificationResolver_104cdb0f1c9.java)

    * $PageSpecificationResolver_104cdb0f1ca.resolve($PageSpecificationResolver_104cdb0f1ca.java)

    * org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:116)
    * $IPageSource_104cdb0f13b.getPage($IPageSource_104cdb0f13b.java)
    * org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java:252)

    * org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java:235)

    * org.apache.tapestry.engine.RequestCycle.activate(RequestCycle.java:596)


I've verified that the application specification is loading and does 
contain the properties

{org.apache.tapestry.component-class-packages and  
org.apache.tapestry.page-class-packages}

Doesn't seem to be stopping it from going to look for the page and 
component specification files.

Is there something still missing? How does the core framework know not 
to look for  page specification. After all, this feature of being able 
to omit the XML is only now possible with the annotation support

Regards,
Phil



Scott F. Walter wrote:

> Phil Zoio wrote:
>
>>
>> With annotation support it seems like it will be possible soon to get 
>> rid of the .page and .jwc altogether.
>>
>> Right now with annotations I'm down to only one piece of information 
>> in my .page and .jwc classes - the name of the class itself. Is there 
>> any way to configure this without using a page or jwc class?
>>
>> Regards,
>> Phil Zoio
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
> Yes you can!  The way you handle the page class name is to add a 
> search path for page/component classes inside your  .application file 
> (which should be located in WEB-INF).  Below is mine:
>
> <?xml version="1.0"?>
>
> <!DOCTYPE application PUBLIC
>  "-//Apache Software Foundation//Tapestry Specification 4.0//EN"
>  "http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd">
>   <application name="Tapestry Component Workbench">
>  <meta key="org.apache.tapestry.template-encoding" value="ISO-8859-1"/>
>  <meta key="org.apache.tapestry.page-class-packages" 
> value="com.scottwalter.sandbox.tapestry4.pages"/>  <meta 
> key="org.apache.tapestry.component-class-packages" 
> value="com.scottwalter.sandbox.tapestry4.components"/>        
>  <library id="contrib" 
> specification-path="/org/apache/tapestry/contrib/Contrib.library"/>
>
> </application>
>
> FYI--I am currently having a problem with making a component (Border 
> in my case) without a .jwc file.  Seems to be a bug that will be fixed 
> in the next beta)
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Tapestry 4 - can we get rid of the .page files?

Posted by "Scott F. Walter" <sc...@scottwalter.com>.
Phil Zoio wrote:

>
> With annotation support it seems like it will be possible soon to get 
> rid of the .page and .jwc altogether.
>
> Right now with annotations I'm down to only one piece of information 
> in my .page and .jwc classes - the name of the class itself. Is there 
> any way to configure this without using a page or jwc class?
>
> Regards,
> Phil Zoio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
Yes you can!  The way you handle the page class name is to add a search 
path for page/component classes inside your  .application file (which 
should be located in WEB-INF).  Below is mine:

<?xml version="1.0"?>

<!DOCTYPE application PUBLIC
  "-//Apache Software Foundation//Tapestry Specification 4.0//EN"
  "http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd">
   
<application name="Tapestry Component Workbench">
  <meta key="org.apache.tapestry.template-encoding" value="ISO-8859-1"/>
  <meta key="org.apache.tapestry.page-class-packages" 
value="com.scottwalter.sandbox.tapestry4.pages"/> 
  <meta key="org.apache.tapestry.component-class-packages" 
value="com.scottwalter.sandbox.tapestry4.components"/> 
        
  <library id="contrib" 
specification-path="/org/apache/tapestry/contrib/Contrib.library"/>
 
</application>

FYI--I am currently having a problem with making a component (Border in 
my case) without a .jwc file.  Seems to be a bug that will be fixed in 
the next beta)


-- 

Scott F. Walter 	Scott F. Walter
Principal Consultant
Vivare, Inc.

E: scott.walter@vivare.com
E: scott@scottwalter.com
Visit scottwalter.com <http://scottwalter.com> --Point.  Click.  Explore!




---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org