>
> I am asking myself whether this is so much better? It would mean
> that we have Alfresco's Web Client (first "webapp") and our
> own Tapestry "webapp" together in one webapp, one JSF-based, the
> other Tapestry-based? Does not sound so nice to me.
It doesn't seem very nice, I see what you mea
On 27.11.2007, at 13:36, adasal wrote:
I've been wondering about this exchange. I haven't looked this up,
but if
this is a problem of sharing across Servlet container contexts then
are you
trying "to do what ought not to be done"?
You are right. A different setup would definitely be more
I've been wondering about this exchange. I haven't looked this up, but if
this is a problem of sharing across Servlet container contexts then are you
trying "to do what ought not to be done"? Why can't you unpack Alfresco and
add in Tapestry to the existing context?
You have access to Alfresco sour
Hi all,
With the help of the list and another insight into the "crossContext"
attribute of Tomcat I've finally found a solution. Thanks for your time!
The deails for my particular application are documented here:
http://wiki.alfresco.com/wiki/
Alfresco_and_Tapestry_on_the_Same_Tomcat_Install
Hi,
I am still working on how to get access, from my Tapestry webapp in
Tomcat,
to a Spring bean called "nodeService" which is from a different
webapp of
Tomcat (Alfresco in this case).
In my previous post, I have run into a problem with the load order:
Alfresco
was loaded by Tomcat after
BTW - I have only used spring 1.2.x. Maybe spring 2.x has a cleaner way of
inter-servlet context bean sharing.
Carlos
--
View this message in context:
http://www.nabble.com/Using-Alfresco-from-within-Tapestry-tf4831087.html#a13861374
Sent from the Tapestry - User mailing list archive at Nabble
hbf wrote:
>
> and everything works beautifully up to the load order of the webapps:
> As my module starts before Alfresco, I cannot reference the (yet non-
> existing) bean of Alfresco that represents the Alfresco Node Service!
>
> . . .
>
> Everything works fine up to the point when I cha
On 20.11.2007, at 07:23, <[EMAIL PROTECTED]> wrote:
If your Tomcat instance is dedicated to alfresco and your tapestry
app,
I would try to go with the shared/lib approach.
Logging in Tomcat is a bit complicated to get right due to the funny
classloading hierarchy and commons-logging's log-met
app's lib *and* common/lib. Then, I need
commons-logging.properties in common/classes to point to log4j as
backend-impl.
> -Original Message-
> From: Kaspar Fischer [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 19, 2007 10:59 PM
> To: Tapestry users
> Subject: Re: U
Marcus, many thanks for your kind reply.
Your link helped me to get started and I think I see the way.
Unfortunately,
I've run into a (Alfresco specific?) problem. But maybe one of you
has run
into a similar one and can help?
The problem is this: Alfresco and my Tapestry webapp run as follo
Have a look at
http://hivemind.apache.org/hivemind1/hivemind-lib/SpringLookupFactory.html
I'm not familiar with Alfresco, but this should get you started with using
any kind of Spring bean from HiveMind (and Tapestry).
You'll probably need to add a couple of hooks to your Tapestry app's
web.xmlto
11 matches
Mail list logo
