You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by joe schacher <di...@gmail.com> on 2014/11/04 19:45:04 UTC
[5.4] Possible error in tapestry-beanvalidator?
Before i begin, a warning. I am not yet an experienced tapestry user. But
5.3.7 is great and works very well for my application!
I have decided to give 5.4 a try. I simply changed my pom.xml to use
5.4-22beta. After making a couple other changes in the pom, and my
hibernate cfg, I run mvn jetty:run-war. I am doing this from inside
intellij idea
This is the only error i get:
java.lang.RuntimeException: Service id 'ValidatorFactory' has already been
defined by
org.apache.tapestry5.beanvalidator.BeanValidatorModule.buildValidatorFactory(BeanValidatorSource,
PropertyShadowBuilder) (at BeanValidatorModule.java:67) and may not be
redefined by
org.apache.tapestry5.beanvalidator.modules.BeanValidatorModule.buildValidatorFactory(BeanValidatorSource,
PropertyShadowBuilder) (at BeanValidatorModule.java:70). You should rename
one of the service builder methods.
Any ideas?
Re: [5.4] Possible error in tapestry-beanvalidator?
Posted by joe schacher <di...@gmail.com>.
Thanks Bob.
This ought to streamline things a bit.
On Tue, Nov 4, 2014 at 9:23 PM, Bob Harner <bo...@gmail.com> wrote:
> Joe,
>
> Incidentally, a goal of jetty:run would be much better than
> jetty:run-war. The jetty:run-war goal incurs the overhead of building
> a war file, and you also won't have live class reloading (one of the
> best things about Tapestry).
>
>
> http://www.eclipse.org/jetty/documentation/current/jetty-maven-plugin.html#jetty-run-goal
>
> On Tue, Nov 4, 2014 at 2:53 PM, joe schacher <di...@gmail.com>
> wrote:
> > thanks, mvn clean package solved that problem!
> >
> > On Tue, Nov 4, 2014 at 2:10 PM, Thiago H de Paula Figueiredo <
> > thiagohp@gmail.com> wrote:
> >
> >> Hi!
> >>
> >> On Tue, 04 Nov 2014 16:45:04 -0200, joe schacher <
> dickleyjones@gmail.com>
> >> wrote:
> >>
> >> java.lang.RuntimeException: Service id 'ValidatorFactory' has already
> been
> >>> defined by
> >>> org.apache.tapestry5.beanvalidator.BeanValidatorModule.
> >>> buildValidatorFactory(BeanValidatorSource,
> >>> PropertyShadowBuilder) (at BeanValidatorModule.java:67) and may not be
> >>> redefined by
> >>> org.apache.tapestry5.beanvalidator.modules.BeanValidatorModule.
> >>> buildValidatorFactory(BeanValidatorSource,
> >>> PropertyShadowBuilder) (at BeanValidatorModule.java:70). You should
> rename
> >>> one of the service builder methods.
> >>>
> >>
> >> You probably have two tapestry-beanvalidator JARs in your classpath.
> Make
> >> sure you only have one.
> >>
> >>
> >>> Any ideas?
> >>>
> >>
> >>
> >> --
> >> Thiago H. de Paula Figueiredo
> >> Tapestry, Java and Hibernate consultant and developer
> >> http://machina.com.br
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: [5.4] Possible error in tapestry-beanvalidator?
Posted by Bob Harner <bo...@gmail.com>.
Joe,
Incidentally, a goal of jetty:run would be much better than
jetty:run-war. The jetty:run-war goal incurs the overhead of building
a war file, and you also won't have live class reloading (one of the
best things about Tapestry).
http://www.eclipse.org/jetty/documentation/current/jetty-maven-plugin.html#jetty-run-goal
On Tue, Nov 4, 2014 at 2:53 PM, joe schacher <di...@gmail.com> wrote:
> thanks, mvn clean package solved that problem!
>
> On Tue, Nov 4, 2014 at 2:10 PM, Thiago H de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
>> Hi!
>>
>> On Tue, 04 Nov 2014 16:45:04 -0200, joe schacher <di...@gmail.com>
>> wrote:
>>
>> java.lang.RuntimeException: Service id 'ValidatorFactory' has already been
>>> defined by
>>> org.apache.tapestry5.beanvalidator.BeanValidatorModule.
>>> buildValidatorFactory(BeanValidatorSource,
>>> PropertyShadowBuilder) (at BeanValidatorModule.java:67) and may not be
>>> redefined by
>>> org.apache.tapestry5.beanvalidator.modules.BeanValidatorModule.
>>> buildValidatorFactory(BeanValidatorSource,
>>> PropertyShadowBuilder) (at BeanValidatorModule.java:70). You should rename
>>> one of the service builder methods.
>>>
>>
>> You probably have two tapestry-beanvalidator JARs in your classpath. Make
>> sure you only have one.
>>
>>
>>> Any ideas?
>>>
>>
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [5.4] Possible error in tapestry-beanvalidator?
Posted by joe schacher <di...@gmail.com>.
thanks, mvn clean package solved that problem!
On Tue, Nov 4, 2014 at 2:10 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> Hi!
>
> On Tue, 04 Nov 2014 16:45:04 -0200, joe schacher <di...@gmail.com>
> wrote:
>
> java.lang.RuntimeException: Service id 'ValidatorFactory' has already been
>> defined by
>> org.apache.tapestry5.beanvalidator.BeanValidatorModule.
>> buildValidatorFactory(BeanValidatorSource,
>> PropertyShadowBuilder) (at BeanValidatorModule.java:67) and may not be
>> redefined by
>> org.apache.tapestry5.beanvalidator.modules.BeanValidatorModule.
>> buildValidatorFactory(BeanValidatorSource,
>> PropertyShadowBuilder) (at BeanValidatorModule.java:70). You should rename
>> one of the service builder methods.
>>
>
> You probably have two tapestry-beanvalidator JARs in your classpath. Make
> sure you only have one.
>
>
>> Any ideas?
>>
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: [5.4] Possible error in tapestry-beanvalidator?
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
Hi!
On Tue, 04 Nov 2014 16:45:04 -0200, joe schacher <di...@gmail.com>
wrote:
> java.lang.RuntimeException: Service id 'ValidatorFactory' has already
> been
> defined by
> org.apache.tapestry5.beanvalidator.BeanValidatorModule.buildValidatorFactory(BeanValidatorSource,
> PropertyShadowBuilder) (at BeanValidatorModule.java:67) and may not be
> redefined by
> org.apache.tapestry5.beanvalidator.modules.BeanValidatorModule.buildValidatorFactory(BeanValidatorSource,
> PropertyShadowBuilder) (at BeanValidatorModule.java:70). You should
> rename
> one of the service builder methods.
You probably have two tapestry-beanvalidator JARs in your classpath. Make
sure you only have one.
>
> Any ideas?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org