Jesse Kuhnert wrote: > I use the ServiceLink quite often but am not as familiar with the > configuration point you are contributing to. For example, tacos plugs > in to > the "tapestry.services.FactoryServices" configuration point to add > special > services: > > http://tacos.svn.sourceforge.net/viewvc/tacos/tacos-4.0/trunk/tacos-core/src/descriptor/META-INF/hivemodule.xml?view=markup >
ok, this might be a bit OT, but i'm commenting here for future reference. I have seen a few differences between FactoryServices and ApplicationServices... IIRC, that was almost a year ago, when testing tacos in portals and i had noticed our ajax service vanishing on certain 'portlet' requests. Contributing to ApplicationServices would somehow fix this, so that's why I did this: http://tacos.cvs.sourceforge.net/tacos/tacos4/src/descriptor/META-INF/hivemodule.xml?r1=1.5&r2=1.6&pathrev=HEAD However, while moving to the SVN (2-3 months later) that changed wasn't picked up... I don't have the time now to redo the portal tests i did back then, but it stills feels right to use ApplicationServices > > On 10/29/06, Dennis Sinelnikov <[EMAIL PROTECTED]> > wrote: >> >> There is a nice example on how to use ServiceLink component with your >> own EngineService in Chapter 8 (Handling File Downloads and Uploads) of >> "Enjoying Web Development w/ Tapestry" book. It also has nice >> explanations on the "flow"... >> >> Dennis >> > > -- Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr Tapestry / Tacos developer Open Source / J2EE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
