Hi,
the Inject annotation moved to the tapestry-ioc project starting from 5.0.6,
maybe you cloud try adding this to your pom.xml?
org.apache.tapestry
tapestry-ioc
5.0.6
James Lin-3 wrote:
>
> thanks your quick reply!
> I could import org.apache.tapestry.services.RequestGl
Hi all,
While migrating a tap4 webapp to tap5, I've come across the following
difference: locale changes are not reflected in the URL. This prevents
Google from indexing translated pages, which is not good.
I used the excellent
http://wiki.apache.org/tapestry/Tapestry5HowToChangeLocale
Tapestry
Hi,
What I had to do:
- change tapestry version in pom.xml from 5.0.5 to 5.0.6
- rename all pages and components to tml
- move pages (not components) to context root (the dir below WEB-INF)
- delete all Inject annotation import statements and let eclipse import the
new Inject
- upgrade log4j to
According to the component reference I copied below, it should be possible to
override the column with a block, and maybe put your radiogroup in the
block. Haven't tried it myself though.
A component that creates an entire form editting the properties of a
particular bean. Inspired by Trails and
Hi all,
I refactored my application to use a new package structure. Unfortunately I
forgot to change the package of the templates in 'src\main\resources' (it
might take some getting used to but there are so many places a
page/component can be in...).
This resulted in a very cryptic error messag
> Hi, i copy & paste this example but it don't work , do i missing something
> ?
Could you post the error? I saw some inline expansions ( ${theLink} ) so
maybe you get the error because you're not running the tapestry
5.0.5-SNAPSHOT release.
--
View this message in context:
http://www.nabble
Hi,
I was copying some google maps javascript
(http://www.google.com/uds/samples/places.html) inside of the head of my
Border component.
Since the javascript code uses < and >, it's protected with //
Hi Sabine,
Another thing to try is issuing a 'mvn -U clean' command. The -U forces
maven to update its dependencies, this could solve the outdated core
problem.
Mike
kristian.marinkovic wrote:
>
> hi sabine,
>
> have you tried to "clean install" everything?
>
> from the stack you can see it