Re: paypal
On Wed, Dec 21, 2011 at 8:05 PM, Chris Mylonas wrote: > after taking most of this year off from deving i'm looking at a project for > early next year. > i'm looking at porting an application that uses PHP stuff (drupal.org + > ubercart.org) to tapestry5 early next year. > the paypal integration is new to me in java, does a library exist already > that just requires the keys put into a file? There's more than one way to skin the Paypal cat. I wouldn't use an implementation that just "requires the keys put into a file". There are lots and lots of different workflows with Paypal depending on what you need. If there was a module available, I'd carefully look into how extensible and customizable it was. > also, apart from session stuff, are there any gotchas that i need to be wary > of for a tapestry web app <---> paypal site? No. For my use case, progressive display worked great (there are several steps to process a payment via Paypal). For server-to-server communication, I used the SOAP api with CXF client & wsdl2java. Kalle - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: ComponentRequestFilter alert a dialog
It is too hard to learn about the Tynamo's Tapestry-security for me. In fact I just want to know how can I alert a dialog in the currentPage through the ComponentRequestFilter. Is there any way. -- View this message in context: http://tapestry.1045711.n5.nabble.com/ComponentRequestFilter-alert-a-dialog-tp5093550p5093713.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
paypal
hi tapestry users, after taking most of this year off from deving i'm looking at a project for early next year. i'm looking at porting an application that uses PHP stuff (drupal.org + ubercart.org) to tapestry5 early next year. the paypal integration is new to me in java, does a library exist already that just requires the keys put into a file? also, apart from session stuff, are there any gotchas that i need to be wary of for a tapestry web app <---> paypal site? thanks for any help cheers chris - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: ComponentRequestFilter alert a dialog
yes. and lots more. On Dec 21, 2011, at 10:42 PM, dick_hu wrote: > > lprimak wrote >> >> Why don't you use the wonderful Tynamo's Tapestry-security? >> >> > It can alert a dialog when it can't pass the filter? - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: ComponentRequestFilter alert a dialog
lprimak wrote > > Why don't you use the wonderful Tynamo's Tapestry-security? > > It can alert a dialog when it can't pass the filter? -- View this message in context: http://tapestry.1045711.n5.nabble.com/ComponentRequestFilter-alert-a-dialog-tp5093550p5093561.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: ComponentRequestFilter alert a dialog
Why don't you use the wonderful Tynamo's Tapestry-security? On Dec 21, 2011, at 10:33 PM, dick_hu wrote: > Now I'm is develop a AuthenticationFilter, If user browse the page when he > did not login the web,the filter where alert a dialog in the current > page,and then user input his username and password in the dialog form then > skip to the page (best the page will not refresh). I know how the filter > redirect to the login page when users didn't logined. But I don't know how > the filter can alert a dialog. > Can anyone help me. Are there any examples for me ,thanks a lot. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/ComponentRequestFilter-alert-a-dialog-tp5093550p5093550.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
ComponentRequestFilter alert a dialog
Now I'm is develop a AuthenticationFilter, If user browse the page when he did not login the web,the filter where alert a dialog in the current page,and then user input his username and password in the dialog form then skip to the page (best the page will not refresh). I know how the filter redirect to the login page when users didn't logined. But I don't know how the filter can alert a dialog. Can anyone help me. Are there any examples for me ,thanks a lot. -- View this message in context: http://tapestry.1045711.n5.nabble.com/ComponentRequestFilter-alert-a-dialog-tp5093550p5093550.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [ANNOUNCE] Announcing Tapestry 5.3.1
On Wed, Dec 21, 2011 at 11:43 PM, jose luis sanchez wrote: > No binary package available yet … 8-( I'm not sure where you were looking for but you can find it in the central maven repo: http://search.maven.org/#artifactdetails%7Corg.apache.tapestry%7Ctapestry5-annotations%7C5.3.1%7Cjar and on Apache main distribution: http://www.apache.org/dist/tapestry/apache-tapestry-5.3.1-sources.zip Maybe the archives need to reach every single mirror but it should a matters of hours... Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [ANNOUNCE] Announcing Tapestry 5.3.1
No binary package available yet … 8-( Anyway, congratulations for the release :) El 21/12/2011, a las 23:29, Massimo Lusetti escribió: > > The Tapestry Team is very proud to announce the availability of Apache > Tapestry 5.3.1. > > http://tapestry.apache.org/2011/12/21/announcing-tapestry-531.html > > Tapestry is primarily available for download via Maven, from the Maven > central repository: > > Maven Dependency > > org.apache.tapestry > tapestry-core > 5.3.1 > > > You can also download the source or JavaDocs archives. > > Tapestry 5.3.1 is mainly a bug fix release and represents a drop in > replacement for the previous stable 5.3. > Full details are in the release notes, but here's a few highlights > plus the ones from 5.3: > > @PerThread scope honored when service is created using autobuild > @ActivationRequestParameter encoded to be URL friendly > Exceptions while compressing JavaScript are fully reported > All forms/submission working normally after FileUploadException is raised > Asset path prefix configurable > > As usual for each Tapestry5 releases we've made great efforts to > ensure and easy upgrade path, anyway, be sure to read the upgrade > notes carefully as some interfaces and methods that were deprecated in > Tapestry 5.0 or 5.1 have been removed: you should recompile and retest > your application after upgrading your dependency. If you still have > problems, use the Tapestry user mailing list to get support. > > Have fun! > -- > Massimo > http://meridio.blogspot.com > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [ANNOUNCE] Announcing Tapestry 5.3.1
Congratulations on a release well done! On Dec 21, 2011, at 5:29 PM, Massimo Lusetti wrote: > The Tapestry Team is very proud to announce the availability of Apache > Tapestry 5.3.1. > > http://tapestry.apache.org/2011/12/21/announcing-tapestry-531.html > > Tapestry is primarily available for download via Maven, from the Maven > central repository: > > Maven Dependency > > org.apache.tapestry > tapestry-core > 5.3.1 > > > You can also download the source or JavaDocs archives. > > Tapestry 5.3.1 is mainly a bug fix release and represents a drop in > replacement for the previous stable 5.3. > Full details are in the release notes, but here's a few highlights > plus the ones from 5.3: > > @PerThread scope honored when service is created using autobuild > @ActivationRequestParameter encoded to be URL friendly > Exceptions while compressing JavaScript are fully reported > All forms/submission working normally after FileUploadException is raised > Asset path prefix configurable > > As usual for each Tapestry5 releases we've made great efforts to > ensure and easy upgrade path, anyway, be sure to read the upgrade > notes carefully as some interfaces and methods that were deprecated in > Tapestry 5.0 or 5.1 have been removed: you should recompile and retest > your application after upgrading your dependency. If you still have > problems, use the Tapestry user mailing list to get support. > > Have fun! > -- > Massimo > http://meridio.blogspot.com > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
[ANNOUNCE] Announcing Tapestry 5.3.1
The Tapestry Team is very proud to announce the availability of Apache Tapestry 5.3.1. http://tapestry.apache.org/2011/12/21/announcing-tapestry-531.html Tapestry is primarily available for download via Maven, from the Maven central repository: Maven Dependency org.apache.tapestry tapestry-core 5.3.1 You can also download the source or JavaDocs archives. Tapestry 5.3.1 is mainly a bug fix release and represents a drop in replacement for the previous stable 5.3. Full details are in the release notes, but here's a few highlights plus the ones from 5.3: @PerThread scope honored when service is created using autobuild @ActivationRequestParameter encoded to be URL friendly Exceptions while compressing JavaScript are fully reported All forms/submission working normally after FileUploadException is raised Asset path prefix configurable As usual for each Tapestry5 releases we've made great efforts to ensure and easy upgrade path, anyway, be sure to read the upgrade notes carefully as some interfaces and methods that were deprecated in Tapestry 5.0 or 5.1 have been removed: you should recompile and retest your application after upgrading your dependency. If you still have problems, use the Tapestry user mailing list to get support. Have fun! -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Issues / feature requests for tapestry-security?
Hello, this is perfect timing for us! Just a week ago, we considered using tynamo-federatedaccounts for our new app (big one). We have already a tapestry 5 based openid server, so tynamo-federatedaccounts with openid realm would be a natural fit. As noted on the website, the support for openid is planned for version 0.0.3. Too late :-) we implemented it - so we can share the code back to the project if you wish. Currently we can sign-in into our webapp with facebook, our openid server and google account. We think it would be nice if LinkedIn would be supported too. There are some open questions, we can discuss if you want. -borut 2011/12/20 Kalle Korhonen > After grueling six months of development on Android, I'm back at the > server side. I'll be cutting a new, T5.3 specific version of Tynamo's > tapestry-security in the near future, though unfortunately it won't > make it to Santa's sleigh. I'm hoping to also pick up Shiro 1.2 as a > dependency if we get that finalized in time. If there's anything you > really wanted to change or fix in tapestry-security but never got > around reporting it, right about now would be a good time. All the > currently open issues will be resolved as well. Thanks to all, it's > been a great year for Tapestry! > > Kalle > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: How to handle urls for a White Label site
On Wed, 21 Dec 2011 15:02:30 -0200, Cezary Biernacki wrote: In Tapestry 5.1 you need to contribute 'URLRewriteRule'-s to URLRewriter service. URLRewriter works in T5.2 too, but it is deprecated, Correct. so in Tapestry 5.2 and 5.3 you need to decorate ComponentEventLinkEncoder. Not correct. The old URL rewriting rule was replaced by the LinkTransformer API, so there's absolutely no need to decorate ComponentEventLinkEncoder yourself. More details here: http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Documentation for tapestry-core
On Wed, 21 Dec 2011 14:53:54 -0200, Dimitris Zenios wrote: I prefer tapestry-ioc over any other ioc implementation.Thats why i would like to understand a little bit more about how everything is connected.Sure anyone can initiate the ioc in some simple manner but for more advanced things like type coercers,class transformations,instantiators,invalidation hubs, things get little bit trickier and sometimes i find it difficult to follow it in the source code of tapestry-core with so much abstraction happening. Ask questions about specific things and you'll get more and better answers than a generic one like your original. ;) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: How to handle urls for a White Label site
Hi, I have built a quite large white-label web app using Tapestry 5, and I am aware of other white-label Tapestry-based sites. I recommend following approach: - Encode partner information in URL for (nearly) all your pages, not only 'gateway' ones. I use 'http://example.com/PARTNER/PAGE'. - If necessary, put some pages that are not partner-dependent in a separate package. - Write code that performs URL rewriting for both incoming and outgoing links. In Tapestry 5.1 you need to contribute 'URLRewriteRule'-s to URLRewriter service. URLRewriter works in T5.2 too, but it is deprecated, so in Tapestry 5.2 and 5.3 you need to decorate ComponentEventLinkEncoder. Remember to not-rewrite requests to '/assets/' and your special package (or packages). - Your code after rewriting URL, should store information about partner as 'Request' attribute. It is important to NOT store that in the session, otherwise you would invite problems like e.g. loosing partner branding when the session expires. - Write a service that provides a nice interface for getting information about the current partner from the request. - If you feel especially adventurous and not afraid of Tapestry internals, you can even write an InjectionProvider and/or ComponentClassTransformWorker to automagically inject necessary data about partner into your pages and class. However, it is not recommended for beginners, and please do not overuse such mechanism, as it could make your code hard to understand for less Tapestry-proficient developers. Best regards, Cezary On Wed, Dec 21, 2011 at 1:08 PM, captain_rhino < graeme.kitc...@axa-travel-insurance.com> wrote: > A little xmas cheer to all! > > I'm in the process of creating a white label site to handle insurance > claims > for different partners. > > I'm looking for a general steer on how to handle the urls. > > The web page flow is generic for all the different white label partners. > > Currently external sites use the following links to access my site > www.mydomain.com/makeaclaim/whitelabelpartner1 > www.mydomain.com/makeaclaim/whitelabelpartner2 > > for a white label partner entering our site I use a > PageRenderLinkTransformer to then look at the that url and move them onto > to > the start of the journey and store where they came from in the session. > i.e. move them from > www.mydomain.com/makeaclaim/whitelabelpartner1 > to > www.mydomain.com/makeaclaim/claimdetails > > > My problem is if they bookmark the claimsdetails or any future page links I > have no idea where they came from. I have thought of passing a request > parameter through the entire journey but that seems a bit clunky. > Ideally i'd like to be to do the following > > www.mydomain.com/makeaclaim/whitelabelpartner1/claimdetails > www.mydomain.com/makeaclaim/whitelabelpartner1/personaldetails > > www.mydomain.com/makeaclaim/whitelabelpartner2/claimdetails > www.mydomain.com/makeaclaim/whitelabelpartner2/personaldetails > > where claim details is one single tapestry page not placed in two separate > packages as this needs to be configurable as new partners can be added all > the time. > > Is some kind of url masking to page actions available in tapestry? > i.e. > www.mydomain.com/makeaclaim/*/claimdetails > > Any ideas/Suggestions welcome. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/How-to-handle-urls-for-a-White-Label-site-tp5091687p5091687.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: Documentation for tapestry-core
I prefer tapestry-ioc over any other ioc implementation.Thats why i would
like to understand a little bit more about how everything is connected.Sure
anyone can initiate the ioc in some simple manner but for more advanced
things like type coercers,class transformations,instantiators,invalidation
hubs, things get little bit trickier and sometimes i find it difficult to
follow it in the source code of tapestry-core with so much abstraction
happening.
On Wed, Dec 21, 2011 at 6:36 PM, Dmitriy Vsekhvalnov wrote:
> well, i'm using tapestry-ioc alone with several projects, may be around
> ~10. I perfer it by many means to Spring as i were doing before with
> HiveMind.
>
> Here is how it is typically looks like with my projects:
>
> pom.xml
>
>
>org.apache.tapestry
>tapestry-ioc
>5.1.0.5
>
>
> Somewhere in the servlet init class (or may be Main class or any other
> entry point to your app):
>
>RegistryBuilder builder = new RegistryBuilder();
>builder.add(ServerModule.class); //add your own module
>builder.add(HibernateCoreModule.class); //add some other 3rd
> party or yours module, why not Hibernate :)
>
> And bind everything together in your ServerModule:
>
> public class ServerModule
> {
>private static final Logger slog = LoggerFactory.getLogger("SERVER");
>private static final Logger elog = LoggerFactory.getLogger("ERROR");
>
>public static void bind(ServiceBinder binder)
>{
>binder.bind(...);
>}
> }
>
> Have fun :)
>
>
>
>
>
>
> On Wed, Dec 21, 2011 at 7:19 PM, Dimitris Zenios
> wrote:
>
> > Maybe someone has to write a page on how tapestry core-works and how it
> > links tapestry-ioc with web applications.Many including me want to used
> > tapestry-ioc into their own applications but some times i find it very
> > difficult to understand how everything glues together in
> tapestry-core.Some
> > things just work automagically :)
> >
>
Re: Documentation for tapestry-core
well, i'm using tapestry-ioc alone with several projects, may be around
~10. I perfer it by many means to Spring as i were doing before with
HiveMind.
Here is how it is typically looks like with my projects:
pom.xml
org.apache.tapestry
tapestry-ioc
5.1.0.5
Somewhere in the servlet init class (or may be Main class or any other
entry point to your app):
RegistryBuilder builder = new RegistryBuilder();
builder.add(ServerModule.class); //add your own module
builder.add(HibernateCoreModule.class); //add some other 3rd
party or yours module, why not Hibernate :)
And bind everything together in your ServerModule:
public class ServerModule
{
private static final Logger slog = LoggerFactory.getLogger("SERVER");
private static final Logger elog = LoggerFactory.getLogger("ERROR");
public static void bind(ServiceBinder binder)
{
binder.bind(...);
}
}
Have fun :)
On Wed, Dec 21, 2011 at 7:19 PM, Dimitris Zenios
wrote:
> Maybe someone has to write a page on how tapestry core-works and how it
> links tapestry-ioc with web applications.Many including me want to used
> tapestry-ioc into their own applications but some times i find it very
> difficult to understand how everything glues together in tapestry-core.Some
> things just work automagically :)
>
Re: Documentation for tapestry-core
Some very good examples of how to use tapestry-ioc are the tapestry-hibernate-core tests. I think that is enough to get you started. Rest nothing can explain you the tapestry code better than the tapestry code itself. regards Taha On Dec 21, 2011, at 9:49 PM, Dimitris Zenios wrote: > Maybe someone has to write a page on how tapestry core-works and how it > links tapestry-ioc with web applications.Many including me want to used > tapestry-ioc into their own applications but some times i find it very > difficult to understand how everything glues together in tapestry-core.Some > things just work automagically :) - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Documentation for tapestry-core
Maybe someone has to write a page on how tapestry core-works and how it links tapestry-ioc with web applications.Many including me want to used tapestry-ioc into their own applications but some times i find it very difficult to understand how everything glues together in tapestry-core.Some things just work automagically :)
Re: How to handle urls for a White Label site
1. You would want to use tapestry's URL rewriting support to remove "whitelabelpartnerX" from the URL before passing it down the request processing pipeline. 2. As your URLRewriterRule removes the whitelabelpartner from the url, it should push it onto the Environment so that it can be accessed later. This can be done by @inject-ing the Environment and calling environment.push(new WhitelabelPartner(partnerValueFromUrl)); 3. Your layout component (and other pages / components) can then use the @Environmental annotation to get the WhitelabelPartner instance from the stack and style the page / provide priviledges accordingly Links http://tapestry.apache.org/url-rewriting.html http://tapestry.apache.org/request-processing.html http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/Environment.html http://tapestry.apache.org/environmental-services.html On Wednesday, 21 December 2011, captain_rhino < graeme.kitc...@axa-travel-insurance.com> wrote: > A little xmas cheer to all! > > I'm in the process of creating a white label site to handle insurance claims > for different partners. > > I'm looking for a general steer on how to handle the urls. > > The web page flow is generic for all the different white label partners. > > Currently external sites use the following links to access my site > www.mydomain.com/makeaclaim/whitelabelpartner1 > www.mydomain.com/makeaclaim/whitelabelpartner2 > > for a white label partner entering our site I use a > PageRenderLinkTransformer to then look at the that url and move them onto to > the start of the journey and store where they came from in the session. > i.e. move them from > www.mydomain.com/makeaclaim/whitelabelpartner1 > to > www.mydomain.com/makeaclaim/claimdetails > > > My problem is if they bookmark the claimsdetails or any future page links I > have no idea where they came from. I have thought of passing a request > parameter through the entire journey but that seems a bit clunky. > Ideally i'd like to be to do the following > > www.mydomain.com/makeaclaim/whitelabelpartner1/claimdetails > www.mydomain.com/makeaclaim/whitelabelpartner1/personaldetails > > www.mydomain.com/makeaclaim/whitelabelpartner2/claimdetails > www.mydomain.com/makeaclaim/whitelabelpartner2/personaldetails > > where claim details is one single tapestry page not placed in two separate > packages as this needs to be configurable as new partners can be added all > the time. > > Is some kind of url masking to page actions available in tapestry? > i.e. > www.mydomain.com/makeaclaim/*/claimdetails > > Any ideas/Suggestions welcome. > > -- > View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-handle-urls-for-a-White-Label-site-tp5091687p5091687.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: How to handle urls for a White Label site
I have not used this but I think it does what you want. http://tynamo.org/tapestry-routing+guide -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-handle-urls-for-a-White-Label-site-tp5091687p5092265.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
How to handle urls for a White Label site
A little xmas cheer to all! I'm in the process of creating a white label site to handle insurance claims for different partners. I'm looking for a general steer on how to handle the urls. The web page flow is generic for all the different white label partners. Currently external sites use the following links to access my site www.mydomain.com/makeaclaim/whitelabelpartner1 www.mydomain.com/makeaclaim/whitelabelpartner2 for a white label partner entering our site I use a PageRenderLinkTransformer to then look at the that url and move them onto to the start of the journey and store where they came from in the session. i.e. move them from www.mydomain.com/makeaclaim/whitelabelpartner1 to www.mydomain.com/makeaclaim/claimdetails My problem is if they bookmark the claimsdetails or any future page links I have no idea where they came from. I have thought of passing a request parameter through the entire journey but that seems a bit clunky. Ideally i'd like to be to do the following www.mydomain.com/makeaclaim/whitelabelpartner1/claimdetails www.mydomain.com/makeaclaim/whitelabelpartner1/personaldetails www.mydomain.com/makeaclaim/whitelabelpartner2/claimdetails www.mydomain.com/makeaclaim/whitelabelpartner2/personaldetails where claim details is one single tapestry page not placed in two separate packages as this needs to be configurable as new partners can be added all the time. Is some kind of url masking to page actions available in tapestry? i.e. www.mydomain.com/makeaclaim/*/claimdetails Any ideas/Suggestions welcome. -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-handle-urls-for-a-White-Label-site-tp5091687p5091687.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
