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/1
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).
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
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 t
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
