You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Geoff Longman <gl...@intelligentworks.com> on 2004/01/07 18:49:57 UTC
[SOLVED]Re: Is there another way to instantiate Global?
Here's how I fixed it.
create a lib dir under WEB-INF - put the perst jar there.
Open the Jetty run configuration and select the classpath tab.
uncheck "use default classpath"
remove the reference to perst.jar from the classpath - Jetty will pick it up
'cuz its in /lib
run it.
It should work fine.
The default behaviour of the Jetty Plugin is to add the all the entries in
the projects build path into the classpath that Jetty runs in. In this case
you don't want that to happen.
Geoff
----- Original Message -----
From: "F. Da Costa" <da...@xs4all.nl>
To: <ta...@jakarta.apache.org>
Sent: Wednesday, January 07, 2004 12:39 PM
Subject: Re: Is there another way to instantiate Global?
> Adam Greene wrote:
>
> > PERST uses some kind of custom built Persistance model other than
> > Serializable, that might be part of the problem. I don't know as I
haven't
> > used pERST, just read the webpage.
> Fair enough but *if* that were a problem it would have had to pop up much
> earlier already.
> Combine that with the fact that Tapestry and Perst do not touch each other
> other than through a parameter in Global I would be highly surprised
indeed.
> Also its a very small embedded db. Being embeddable i would assume you
take
> out most if not all the teeth for biting the embedding app.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [THX]Re: Is there another way to instantiate Global?
Posted by "F. Da Costa" <da...@xs4all.nl>.
Geoff Longman wrote:
> Here's how I fixed it.
>
> create a lib dir under WEB-INF - put the perst jar there.
This is totally cool. You basically fixed it in the amount of the time it
takes me to whip up some food.
mentioning the /lib dir gves me a feel for the used to but not any more line.
The dirty project was *not* Spindleized *and* doubling for Tomcat as well
and for TC I needed to have the jars in place.
I can probably stop here, can't I?
> It should work fine.
It most definitely does.
Thx, again
Fermin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [SOLVED]Re: Is there another way to instantiate Global?
Posted by Geoff Longman <gl...@intelligentworks.com>.
I woulda said D'oh!
:-)
----- Original Message -----
From: "Adam Greene" <ag...@romulin.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Wednesday, January 07, 2004 1:09 PM
Subject: RE: [SOLVED]Re: Is there another way to instantiate Global?
> Let me rephrase that so that people do not think I am calling them names
:-)
>
> "Silly me, I should have thought of that as I have already seen that
> problem"
>
> :-)
>
> -----Original Message-----
> From: Adam Greene [mailto:agreene@romulin.com]
> Sent: Wednesday, January 07, 2004 1:58 PM
> To: Tapestry users
> Subject: RE: [SOLVED]Re: Is there another way to instantiate Global?
>
>
> Duh! We had the same problem with another library (we were getting
Linkage
> Errors).
>
> -----Original Message-----
> From: Geoff Longman [mailto:glongman@intelligentworks.com]
> Sent: Wednesday, January 07, 2004 1:50 PM
> To: Tapestry users
> Subject: [SOLVED]Re: Is there another way to instantiate Global?
>
>
> Here's how I fixed it.
>
> create a lib dir under WEB-INF - put the perst jar there.
>
> Open the Jetty run configuration and select the classpath tab.
>
> uncheck "use default classpath"
>
> remove the reference to perst.jar from the classpath - Jetty will pick it
up
> 'cuz its in /lib
>
> run it.
>
> It should work fine.
>
> The default behaviour of the Jetty Plugin is to add the all the entries in
> the projects build path into the classpath that Jetty runs in. In this
case
> you don't want that to happen.
>
> Geoff
> ----- Original Message -----
> From: "F. Da Costa" <da...@xs4all.nl>
> To: <ta...@jakarta.apache.org>
> Sent: Wednesday, January 07, 2004 12:39 PM
> Subject: Re: Is there another way to instantiate Global?
>
>
> > Adam Greene wrote:
> >
> > > PERST uses some kind of custom built Persistance model other than
> > > Serializable, that might be part of the problem. I don't know as I
> haven't
> > > used pERST, just read the webpage.
> > Fair enough but *if* that were a problem it would have had to pop up
much
> > earlier already.
> > Combine that with the fact that Tapestry and Perst do not touch each
other
> > other than through a parameter in Global I would be highly surprised
> indeed.
> > Also its a very small embedded db. Being embeddable i would assume you
> take
> > out most if not all the teeth for biting the embedding app.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: [SOLVED]Re: Is there another way to instantiate Global?
Posted by Adam Greene <ag...@romulin.com>.
Let me rephrase that so that people do not think I am calling them names :-)
"Silly me, I should have thought of that as I have already seen that
problem"
:-)
-----Original Message-----
From: Adam Greene [mailto:agreene@romulin.com]
Sent: Wednesday, January 07, 2004 1:58 PM
To: Tapestry users
Subject: RE: [SOLVED]Re: Is there another way to instantiate Global?
Duh! We had the same problem with another library (we were getting Linkage
Errors).
-----Original Message-----
From: Geoff Longman [mailto:glongman@intelligentworks.com]
Sent: Wednesday, January 07, 2004 1:50 PM
To: Tapestry users
Subject: [SOLVED]Re: Is there another way to instantiate Global?
Here's how I fixed it.
create a lib dir under WEB-INF - put the perst jar there.
Open the Jetty run configuration and select the classpath tab.
uncheck "use default classpath"
remove the reference to perst.jar from the classpath - Jetty will pick it up
'cuz its in /lib
run it.
It should work fine.
The default behaviour of the Jetty Plugin is to add the all the entries in
the projects build path into the classpath that Jetty runs in. In this case
you don't want that to happen.
Geoff
----- Original Message -----
From: "F. Da Costa" <da...@xs4all.nl>
To: <ta...@jakarta.apache.org>
Sent: Wednesday, January 07, 2004 12:39 PM
Subject: Re: Is there another way to instantiate Global?
> Adam Greene wrote:
>
> > PERST uses some kind of custom built Persistance model other than
> > Serializable, that might be part of the problem. I don't know as I
haven't
> > used pERST, just read the webpage.
> Fair enough but *if* that were a problem it would have had to pop up much
> earlier already.
> Combine that with the fact that Tapestry and Perst do not touch each other
> other than through a parameter in Global I would be highly surprised
indeed.
> Also its a very small embedded db. Being embeddable i would assume you
take
> out most if not all the teeth for biting the embedding app.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: [SOLVED]Re: Is there another way to instantiate Global?
Posted by Adam Greene <ag...@romulin.com>.
Duh! We had the same problem with another library (we were getting Linkage
Errors).
-----Original Message-----
From: Geoff Longman [mailto:glongman@intelligentworks.com]
Sent: Wednesday, January 07, 2004 1:50 PM
To: Tapestry users
Subject: [SOLVED]Re: Is there another way to instantiate Global?
Here's how I fixed it.
create a lib dir under WEB-INF - put the perst jar there.
Open the Jetty run configuration and select the classpath tab.
uncheck "use default classpath"
remove the reference to perst.jar from the classpath - Jetty will pick it up
'cuz its in /lib
run it.
It should work fine.
The default behaviour of the Jetty Plugin is to add the all the entries in
the projects build path into the classpath that Jetty runs in. In this case
you don't want that to happen.
Geoff
----- Original Message -----
From: "F. Da Costa" <da...@xs4all.nl>
To: <ta...@jakarta.apache.org>
Sent: Wednesday, January 07, 2004 12:39 PM
Subject: Re: Is there another way to instantiate Global?
> Adam Greene wrote:
>
> > PERST uses some kind of custom built Persistance model other than
> > Serializable, that might be part of the problem. I don't know as I
haven't
> > used pERST, just read the webpage.
> Fair enough but *if* that were a problem it would have had to pop up much
> earlier already.
> Combine that with the fact that Tapestry and Perst do not touch each other
> other than through a parameter in Global I would be highly surprised
indeed.
> Also its a very small embedded db. Being embeddable i would assume you
take
> out most if not all the teeth for biting the embedding app.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org