Re: Libarary "core" mapping not working in 5.2.0-SNAPSHOT
wait, so we can't map libraries onto the "core" prefix? Can we map it into a "" prefix? The issue is that we leveraged that capability to essentially bring our libraries all under the same namespace.. To make accessing common/shared components easier to code against.. instead of On 8/13/10 5:38 PM, Thiago H. de Paula Figueiredo wrote: On Fri, 13 Aug 2010 20:09:49 -0300, raulmt wrote: named ViewCore inside the core package). If using the core library mapping will not be permited anymore, what would be the best way to preserve or at least redirect existing links like the previous one? Use LinkTransformer (URL rewriting). - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Libarary "core" mapping not working in 5.2.0-SNAPSHOT
On Fri, 13 Aug 2010 20:09:49 -0300, raulmt wrote: named ViewCore inside the core package). If using the core library mapping will not be permited anymore, what would be the best way to preserve or at least redirect existing links like the previous one? Use LinkTransformer (URL rewriting). -- 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: Libarary "core" mapping not working in 5.2.0-SNAPSHOT
I wanted to switch to T5.2, and I found exactly this problem. I have an app with many modules, and one of them is the "CoreModule", which maps all its components to the LibraryMapping "core". In Tapestry documentation, it says: Note: it is possible to add a mapping for "core". "core" is the core library for Tapestry components; all the built-in Tapestry components (TextField, BeanEditForm, Grid, etc.) are actually in the core library. All Tapestry does is search inside the "core" library when it does find a component in the application. Contributing an additional package as "core" simply extends the number of packages searched for core components (it doesn't replace Tapestry's default package, org.apache.tapestry5.corelib). Adding to "core" is sometimes reasonable, if there is virtually no chance of a naming conflict (via different modules contributing packages to core with conflicting class names). So I didn't think this could cause future problems… I don't mind changing all the code inside my app to change the library mapping, BUT the bad side of this is that many links will stop working… The principal page of my application is like http://www.example.org/core/view/id_of_resource (a page named ViewCore inside the core package). If using the core library mapping will not be permited anymore, what would be the best way to preserve or at least redirect existing links like the previous one? Regards, Raul. -- View this message in context: http://tapestry-users.832.n2.nabble.com/Libarary-core-mapping-not-working-in-5-2-0-SNAPSHOT-tp5132139p5421946.html Sent from the Tapestry Users 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: Libarary "core" mapping not working in 5.2.0-SNAPSHOT
This might be a bug, but is not easily fixable. Contributing new components into core strikes me as a somewhat dangerous proposition. On Wed, Jun 2, 2010 at 12:10 PM, Manuel Sugawara wrote: > Hi, > > I have a library that uses the core mapping but a few days ago > this stopped working. Tapestry throws an exception saying "Package names for > library folder 'core' (mx.unam.xfc.escuela.t5, org.apache.tapestry5.corelib) > can not be reduced to a common base package (of at least two terms)." As > this was reported before but got no answer I will try again. Is this not > supported anymore?, Is this a bug?, Should I create a Jira issue?. > > Regards, > Manuel. > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Libarary "core" mapping not working in 5.2.0-SNAPSHOT
Hi, I have a library that uses the core mapping but a few days ago this stopped working. Tapestry throws an exception saying "Package names for library folder 'core' (mx.unam.xfc.escuela.t5, org.apache.tapestry5.corelib) can not be reduced to a common base package (of at least two terms)." As this was reported before but got no answer I will try again. Is this not supported anymore?, Is this a bug?, Should I create a Jira issue?. Regards, Manuel.
