In fact it works well with Tapestry 5.1.0.5. I just missed to activate
correctly the Compatibilty Mode. I believed it was via AppModule using
configuration.add(SpringConstants.USE_EXTERNAL_SPRING_CONTEXT, "true"); but
it must be in the web.xml :
tapestry.use-external-sprin
Hi,
I'm facing the same issue, ie. I want to inject a Spring Bean an there
is more than one Spring Bean that implement the declared interface. In
my Spring Bean in such case, I use the Spring Bean ID to specify which
one I want.
I understand it is not possible yet with Tapestry 5, but it is maybe
Captain Cid,
the Tapestry spring integration cannot handle injecting a bean when there
is more than one bean of the given type defined in Spring (as the error
message says). Your option there is to inject the factory bean into your T5
page, and then use that to retrieve the instance you need. T5
Can you post your code for the Configuration and Process classes?
On Thu, May 6, 2010 at 11:24 AM, Captain Cid wrote:
>
> Can anyone please look into this
>
> Thanks
>
>
> Captain Cid wrote:
> >
> > I even tried
> >
> > @Inject
> > @Service("process")
> > private Process process;
> >
> > Caused b
Can anyone please look into this
Thanks
Captain Cid wrote:
>
> I even tried
>
> @Inject
> @Service("process")
> private Process process;
>
> Caused by: java.lang.RuntimeException: Service id 'Process' is not defined
> by any module.
>
> I am only using this configuration file to load be
I even tried
@Inject
@Service("process")
private Process process;
Caused by: java.lang.RuntimeException: Service id 'Process' is not defined
by any module.
I am only using this configuration file to load beans...so i guess there
should not be a confusion or second possibility
Michael Presc
Re: the first error, it looks like Spring is trying to inject your class 'by
type', but isn't sure which of two Process beans to use. I only see one
from the snippet you've attached, is it possible that there's another one?
As far as the second error goes, the ids are probably case sensitive -
'P
