You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Wolfgang Egger <wo...@beaglesoft.biz> on 2002/10/07 12:00:51 UTC
IFrames
Servus all out there,
I'm not sure if this is he right mailing-list, but perhaps you can give
me some hints, what resources I should look at to solve my problem.
We build a website using IFrames. Now I have to write a test, that
follows all links that are reachable from a given page a page. The links
that are inside of IFrames and the sources of the IFrames self, has to
be followed too. I have tried httpUnit, but it doesn't recognize
IFrames. I took a look at the cactus documentation, but it seems, that
this is the wrong tool, too.
Does everyone know any resources, where I can get an idea, how to test
IFrames automatically?
Have a nice and peacefully day
Wolfgang
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Particular Configuration Problem
Posted by Vincent Massol <vm...@octo.com>.
Vidya,
It really looks like you have already written to the servlet output
stream before you do a forward, which is not allowed by the Servlet
spec. The include will work fine as it does not replace what has already
been sent back but rather adds to it.
-Vincent
> -----Original Message-----
> From: Vidya Deshmukh [mailto:vidyad@bsil.com]
> Sent: 26 October 2002 05:25
> To: 'Cactus Users List'
> Subject: RE: Particular Configuration Problem
>
> Hi Vincent,
> My test gets fail on forward and not getting any session values
> after
> accessing that page which is mentioned in URL ["/test/do-login"]. I
think
> it
> is not accessing that page only. Bust instead of dispatch.forword() if
I
> include dispatch.include() then test case passes but does not show any
> session values as request does not come back from that page. And the
main
> application is coded in cocoon.
>
> > -----Original Message-----
> > From: Vincent Massol [mailto:vmassol@octo.com]
> > Sent: Friday, September 27, 2002 11:54 PM
> > To: 'Cactus Users List'
> > Subject: RE: Cactus wth cocoon help.
> >
> >
> > Vidya,
> >
> > Can you send the stack trace you're getting and the stdout erros
that
> > appear on your server console?
> >
> > I can see one potential issue (but I'm not sure): You are
manipulating
> > the request after you did a forward(). I'm not sure this is allowed
by
> > the Servlet spec.
> >
> > The first thing we need to know is if your test goes past the
> forward()
> > or if it fails on the forward.
> >
> > Question: What does this have to do with Cocoon testing?
> >
> > Cheers,
> > -Vincent
> >
> > > -----Original Message-----
> > > From: Vidya Deshmukh [mailto:vidyad@bsil.com]
> > > Sent: 27 September 2002 06:00
> > > To: 'Cactus Users List'
> > > Subject: RE: Cactus wth cocoon help.
> > >
> > >
> > > Hi Vincent,
> > > I want to test an application which uses cocoon framework , for
> now
> > I
> > > am
> > > just accessing the middle page of application and trying to test
> > wheather
> > > session is valid or present for a perticular user or not. But I am
> not
> > > able
> > > to access that page thro' cactus and rather not getting any
session
> > object
> > > after accessing that page,
> > >
> > > here is my code....
> > >
> > > import junit.framework.Test;
> > > import junit.framework.TestSuite;
> > >
> > > import org.apache.cactus.ServletTestCase;
> > > import org.apache.cactus.WebRequest;
> > > mport javax.servlet.RequestDispatcher;
> > > import javax.servlet.ServletException;
> > > import javax.servlet.http.HttpSession;
> > > import javax.servlet.ServletConfig;
> > >
> > > public class TestLogin extends ServletTestCase
> > > {
> > > public TestLogin(String theName)
> > > {
> > > super(theName);
> > > }
> > >
> > > String loginUrl = "/test/admin/index.jsp";
> > > String logoutUrl = "/test/logout.jsp";
> > > String errMsgUrl = "/test/index.jsp?error='Please Enter Login
and
> > > Password' ";
> > >
> > > /**
> > > * initialize parameters
> > > */
> > > public void beginValidateLogin(WebRequest webRequest)
> > > {
> > > webRequest.addParameter("username", "username");
> > > webRequest.addParameter("password", "passsword");
> > > }
> > >
> > > /**
> > > * test to check wheather session is valid or not and verify
that
> by
> > > * default the session implicit object is available and can be
> used.
> > > */
> > > public void testValidateLogin() throws ServletException
> > > {
> > > try
> > > {
> > >
> > > //ServletConfig theConfig;
> > > RequestDispatcher dispatch =
> > > config.getServletContext().getRequestDispatcher("/test/do-login");
> > > dispatch.forward(request, response);
> > >
> > > HttpSession session = request.getSession(false);
> > > assertNotNull(session);
> > >
> > > // Perform verification that test was successful
> > > assertEquals("username",session.getAttribute("username"));
> > > assertEquals("password",session.getAttribute("password"));
> > > }
> > > catch (Exception ex)
> > > {
> > > System.out.println("Exception" + ex);
> > > // ex.printStackTrace();
> > > } // end of catch
> > > } // end of test method
> > >
> > > /**
> > > * test to check wheather user has successfully logged out.
> > > */
> > > public void testLogout() throws ServletException
> > > {
> > > try
> > > {
> > > RequestDispatcher dispatch =
> > > this.config.getServletContext().getRequestDispatcher(logoutUrl);
> > > dispatch.include(request, response);
> > > assertNotNull(session.getAttribute("username"));
> > > } // end of try
> > > catch (Exception se)
> > > {
> > > System.out.println(se);
> > > } // end of catch
> > >
> > > } // end of test method
> > > public static Test suite()
> > > {
> > > return new TestSuite(TestLogin.class);
> > > }
> > > }
> > >
> > >
> > > Tell me if I am doing anything wrong out here.....
> > >
> > >
> > > -----Original Message-----
> > > From: Vincent Massol [mailto:vmassol@octo.com]
> > > Sent: Thursday, September 26, 2002 3:20 AM
> > > To: 'Cactus Users List'
> > > Subject: RE: Cactus wth cocoon help.
> > >
> > >
> > > Hi Vidya,
> > >
> > > Short answer is yes. What do you want to unit test from Cocoon?
> > >
> > > Thanks
> > > -Vincent
> > >
> > > > -----Original Message-----
> > > > From: Vidya Deshmukh [mailto:vidyad@bsil.com]
> > > > Sent: 25 September 2002 06:14
> > > > To: cactus-user@jakarta.apache.org
> > > > Subject: Cactus wth cocoon help.
> > > >
> > > >
> > > > Hi!
> > > > Can anyone tell me wheater it is possible to Write test cases
> for
> > > > cocoon
> > > > framework? I am trying for it but getting some error while using
> > > > requestDispatcher object, and not able to acces jsp pages and
not
> > > getting
> > > > any request or response or session object from any jsp page.
> > > >
> > > > Regards,
> > > > Vidya
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail: <mailto:cactus-user-
> > > > unsubscribe@jakarta.apache.org>
> > > > For additional commands, e-mail: <mailto:cactus-user-
> > > > help@jakarta.apache.org>
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <ma...@jakarta.apache.org>
> > > For additional commands, e-mail:
> > > <ma...@jakarta.apache.org>
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <mailto:cactus-user-
> > > unsubscribe@jakarta.apache.org>
> > > For additional commands, e-mail: <mailto:cactus-user-
> > > help@jakarta.apache.org>
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Particular Configuration Problem
Posted by Vidya Deshmukh <vi...@bsil.com>.
Hi Vincent,
My test gets fail on forward and not getting any session values after
accessing that page which is mentioned in URL ["/test/do-login"]. I think it
is not accessing that page only. Bust instead of dispatch.forword() if I
include dispatch.include() then test case passes but does not show any
session values as request does not come back from that page. And the main
application is coded in cocoon.
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@octo.com]
> Sent: Friday, September 27, 2002 11:54 PM
> To: 'Cactus Users List'
> Subject: RE: Cactus wth cocoon help.
>
>
> Vidya,
>
> Can you send the stack trace you're getting and the stdout erros that
> appear on your server console?
>
> I can see one potential issue (but I'm not sure): You are manipulating
> the request after you did a forward(). I'm not sure this is allowed by
> the Servlet spec.
>
> The first thing we need to know is if your test goes past the
forward()
> or if it fails on the forward.
>
> Question: What does this have to do with Cocoon testing?
>
> Cheers,
> -Vincent
>
> > -----Original Message-----
> > From: Vidya Deshmukh [mailto:vidyad@bsil.com]
> > Sent: 27 September 2002 06:00
> > To: 'Cactus Users List'
> > Subject: RE: Cactus wth cocoon help.
> >
> >
> > Hi Vincent,
> > I want to test an application which uses cocoon framework , for
now
> I
> > am
> > just accessing the middle page of application and trying to test
> wheather
> > session is valid or present for a perticular user or not. But I am
not
> > able
> > to access that page thro' cactus and rather not getting any session
> object
> > after accessing that page,
> >
> > here is my code....
> >
> > import junit.framework.Test;
> > import junit.framework.TestSuite;
> >
> > import org.apache.cactus.ServletTestCase;
> > import org.apache.cactus.WebRequest;
> > mport javax.servlet.RequestDispatcher;
> > import javax.servlet.ServletException;
> > import javax.servlet.http.HttpSession;
> > import javax.servlet.ServletConfig;
> >
> > public class TestLogin extends ServletTestCase
> > {
> > public TestLogin(String theName)
> > {
> > super(theName);
> > }
> >
> > String loginUrl = "/test/admin/index.jsp";
> > String logoutUrl = "/test/logout.jsp";
> > String errMsgUrl = "/test/index.jsp?error='Please Enter Login and
> > Password' ";
> >
> > /**
> > * initialize parameters
> > */
> > public void beginValidateLogin(WebRequest webRequest)
> > {
> > webRequest.addParameter("username", "username");
> > webRequest.addParameter("password", "passsword");
> > }
> >
> > /**
> > * test to check wheather session is valid or not and verify that
by
> > * default the session implicit object is available and can be
used.
> > */
> > public void testValidateLogin() throws ServletException
> > {
> > try
> > {
> >
> > //ServletConfig theConfig;
> > RequestDispatcher dispatch =
> > config.getServletContext().getRequestDispatcher("/test/do-login");
> > dispatch.forward(request, response);
> >
> > HttpSession session = request.getSession(false);
> > assertNotNull(session);
> >
> > // Perform verification that test was successful
> > assertEquals("username",session.getAttribute("username"));
> > assertEquals("password",session.getAttribute("password"));
> > }
> > catch (Exception ex)
> > {
> > System.out.println("Exception" + ex);
> > // ex.printStackTrace();
> > } // end of catch
> > } // end of test method
> >
> > /**
> > * test to check wheather user has successfully logged out.
> > */
> > public void testLogout() throws ServletException
> > {
> > try
> > {
> > RequestDispatcher dispatch =
> > this.config.getServletContext().getRequestDispatcher(logoutUrl);
> > dispatch.include(request, response);
> > assertNotNull(session.getAttribute("username"));
> > } // end of try
> > catch (Exception se)
> > {
> > System.out.println(se);
> > } // end of catch
> >
> > } // end of test method
> > public static Test suite()
> > {
> > return new TestSuite(TestLogin.class);
> > }
> > }
> >
> >
> > Tell me if I am doing anything wrong out here.....
> >
> >
> > -----Original Message-----
> > From: Vincent Massol [mailto:vmassol@octo.com]
> > Sent: Thursday, September 26, 2002 3:20 AM
> > To: 'Cactus Users List'
> > Subject: RE: Cactus wth cocoon help.
> >
> >
> > Hi Vidya,
> >
> > Short answer is yes. What do you want to unit test from Cocoon?
> >
> > Thanks
> > -Vincent
> >
> > > -----Original Message-----
> > > From: Vidya Deshmukh [mailto:vidyad@bsil.com]
> > > Sent: 25 September 2002 06:14
> > > To: cactus-user@jakarta.apache.org
> > > Subject: Cactus wth cocoon help.
> > >
> > >
> > > Hi!
> > > Can anyone tell me wheater it is possible to Write test cases
for
> > > cocoon
> > > framework? I am trying for it but getting some error while using
> > > requestDispatcher object, and not able to acces jsp pages and not
> > getting
> > > any request or response or session object from any jsp page.
> > >
> > > Regards,
> > > Vidya
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <mailto:cactus-user-
> > > unsubscribe@jakarta.apache.org>
> > > For additional commands, e-mail: <mailto:cactus-user-
> > > help@jakarta.apache.org>
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >
> >
> > --
> > To unsubscribe, e-mail: <mailto:cactus-user-
> > unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: <mailto:cactus-user-
> > help@jakarta.apache.org>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Particular Configuration Problem
Posted by Vincent Massol <vm...@octo.com>.
Marco,
There is now only one official and standard way of deploying
applications in a servlet container: it is the WAR packaging. I would
really recommend you do so. It is *very* to do using Ant (simply use the
Ant war task).
If you still don't want to do that (and I can't think of any reason why
not :-)), then the solution is different for each container. The one you
have seems adequate for Tomcat. Just bear in mind that you will then
have to put all cactus jars in the system classpath (or other top level
classloader). Having a webapp allows to isolate classes and jars as each
webapp has its own classloader.
Hope it helps,
-Vincent
> -----Original Message-----
> From: Marco Barcella [mailto:barcella@appiancorp.com]
> Sent: 08 October 2002 20:35
> To: Cactus Users List
> Subject: RE: Particular Configuration Problem
>
> Thanks,
> one more important question: I am not creating a .war file when I run
the
> test
> with Ant, how can I specify the directory of the
> testing classes I want to run in the build.xml? Right now, although I
> tried to include the myapplication.classes
> ( <pathelement location="${app.classes}"/>) directory in my build.xml,
> I have to put the testing classes in [tomcat home]/common/classes for
them
> to be found. How should I include <pathelement
location="${app.classes}"/>
> so that I can find my own application classes?
>
> Thanks a lot and sorry for asking basic questions,
> marco
>
>
> <>-----Original Message-----
> <>From: Vincent Massol [mailto:vmassol@octo.com]
> <>Sent: Tuesday, October 08, 2002 2:55 AM
> <>To: 'Cactus Users List'
> <>Subject: RE: Particular Configuration Problem
> <>
> <>
> <>
> <>
> <>> -----Original Message-----
> <>> From: Marco Barcella [mailto:barcella@appiancorp.com]
> <>> Sent: 07 October 2002 21:48
> <>> To: Cactus Users List
> <>> Subject: RE: Particular Configuration Problem
> <>>
> <>> Thanks Vincent,
> <>>
> <>> let me make sure I understand one last point:
> <>> I should be able to add the redirector definitions
> <>> to the global web.xml in TOMCAT and avoid modifying
> <>> the production web.xml. Right? So far it seems to work
> <>> but not sure about the future.
> <>
> <>Yes, that does work (and it's quite neat!) because Tomcat does a
"merge"
> <>of both web.xml. It's a Tomcat specific feature and won't work for
all
> <>servlet containers.
> <>
> <>-Vincent
> <>
> <>>
> <>> Thanks a lot for the advices,
> <>> marco
> <>>
> <>> <>-----Original Message-----
> <>> <>From: Vincent Massol [mailto:vmassol@octo.com]
> <>> <>Sent: Monday, October 07, 2002 4:11 PM
> <>> <>To: 'Cactus Users List'
> <>> <>Subject: RE: Particular Configuration Problem
> <>> <>
> <>> <>
> <>> <>Hi Marco,
> <>> <>
> <>> <>> -----Original Message-----
> <>> <>> From: Marco Barcella [mailto:barcella@appiancorp.com]
> <>> <>> Sent: 07 October 2002 20:14
> <>> <>> To: Cactus Users List
> <>> <>> Subject: Particular Configuration Problem
> <>> <>>
> <>> <>> Hi all,
> <>> <>>
> <>> <>> I understand that I am supposed to configure the server side
> <>(web.xml)
> <>> <>> and the client side (cactus.properties: contextURL).
> <>> <>>
> <>> <>> I am using TOMCAT 4.0.3
> <>> <>>
> <>> <>> In my case: I have an application that I deploy to C:/foe/bo/
> <>> <>(deployed
> <>> <>> application);
> <>> <>> this application comes with a web.xml that I can modify adding
the
> <>> <>> redirectors definition, as specified by the website tutorial.
If I
> <>do
> <>> <>that
> <>> <>> everything works, but, ideally I should not modify that
web.xml.
> <>> <>Instead,
> <>> <>> I should create another application (testing application) (in
> <>webapps
> <>> <>for
> <>> <>> example) where I create
> <>> <>> the web.xml which defines the redirectors (instead of
modifying
> <>the
> <>> <>> deployed
> <>> <>> application web.xml) and
> <>> <>> place a build.xml that runs the tests through ANT.
> <>> <>>
> <>> <>
> <>> <>Ideally, yes ... but not in the current cactus. The strategy is
to
> <>have
> <>> <>ant scripts that create 2 wars : one for production and one for
> <>testing.
> <>> <>
> <>> <>> THE PROBLEM is that in order to have the redirectors found, I
have
> <>to
> <>> <>> specify the URLContext to be
> <>> <>> the testing application URL. Therefore I cannot define the
> <>URLContext
> <>> <>to
> <>> <>> be
> <>> <>> the deployed application
> <>> <>> one and therefore I cannot use some methods like
> <>> <>> pageContext.include(relariveURL), testing some files in the
> <>deployed
> <>> <>> application.
> <>> <>
> <>> <>It won't work anyway as one webapp is completely separate from
> <>another
> <>> <>webapp. They live in different realms and cannot call each
other. I
> <>> <>think there is a JSR (or maybe it is the upcoming Servlet API
2.4 ?)
> <>> <>that allows cross-webapp calls but it's definitely not in 2.2
nor
> <>2.3.
> <>> <>
> <>> <>>
> <>> <>> I could define the redirectors in the global web.xml, but I am
> <>trying
> <>> <>to
> <>> <>> avoid that.
> <>> <>> Am I missing something? Is there a way to do what I would like
to
> <>do?
> <>> <>
> <>> <>Yes, by having 2 web.xml and packaging 2 wars. BTW, if you're
> <>concerned
> <>> <>about reuse you can have only one web.xml which gets resolved
> <>> <>differently if you're packaging the test war. See
> <>> <>http://jakarta.apache.org/cactus/faq.html#faq2
> <>> <>
> <>> <>-Vincent
> <>> <>
> <>> <>>
> <>> <>> Thanks in advance,
> <>> <>> marco
> <>> <>>
> <>> <>>
> <>> <>>
> <>> <>>
> <>> <>> --
> <>> <>> To unsubscribe, e-mail: <mailto:cactus-user-
> <>> <>> unsubscribe@jakarta.apache.org>
> <>> <>> For additional commands, e-mail: <mailto:cactus-user-
> <>> <>> help@jakarta.apache.org>
> <>> <>
> <>> <>
> <>> <>
> <>> <>--
> <>> <>To unsubscribe, e-mail:
> <>> <><...@jakarta.apache.org>
> <>> <>For additional commands, e-mail:
> <>> <><...@jakarta.apache.org>
> <>> <>
> <>> <>
> <>>
> <>> --
> <>> To unsubscribe, e-mail: <mailto:cactus-user-
> <>> unsubscribe@jakarta.apache.org>
> <>> For additional commands, e-mail: <mailto:cactus-user-
> <>> help@jakarta.apache.org>
> <>
> <>
> <>
> <>--
> <>To unsubscribe, e-mail:
> <><...@jakarta.apache.org>
> <>For additional commands, e-mail:
> <><...@jakarta.apache.org>
> <>
> <>
>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Particular Configuration Problem
Posted by Marco Barcella <ba...@appiancorp.com>.
Thanks,
one more important question: I am not creating a .war file when I run the
test
with Ant, how can I specify the directory of the
testing classes I want to run in the build.xml? Right now, although I
tried to include the myapplication.classes
( <pathelement location="${app.classes}"/>) directory in my build.xml,
I have to put the testing classes in [tomcat home]/common/classes for them
to be found. How should I include <pathelement location="${app.classes}"/>
so that I can find my own application classes?
Thanks a lot and sorry for asking basic questions,
marco
<>-----Original Message-----
<>From: Vincent Massol [mailto:vmassol@octo.com]
<>Sent: Tuesday, October 08, 2002 2:55 AM
<>To: 'Cactus Users List'
<>Subject: RE: Particular Configuration Problem
<>
<>
<>
<>
<>> -----Original Message-----
<>> From: Marco Barcella [mailto:barcella@appiancorp.com]
<>> Sent: 07 October 2002 21:48
<>> To: Cactus Users List
<>> Subject: RE: Particular Configuration Problem
<>>
<>> Thanks Vincent,
<>>
<>> let me make sure I understand one last point:
<>> I should be able to add the redirector definitions
<>> to the global web.xml in TOMCAT and avoid modifying
<>> the production web.xml. Right? So far it seems to work
<>> but not sure about the future.
<>
<>Yes, that does work (and it's quite neat!) because Tomcat does a "merge"
<>of both web.xml. It's a Tomcat specific feature and won't work for all
<>servlet containers.
<>
<>-Vincent
<>
<>>
<>> Thanks a lot for the advices,
<>> marco
<>>
<>> <>-----Original Message-----
<>> <>From: Vincent Massol [mailto:vmassol@octo.com]
<>> <>Sent: Monday, October 07, 2002 4:11 PM
<>> <>To: 'Cactus Users List'
<>> <>Subject: RE: Particular Configuration Problem
<>> <>
<>> <>
<>> <>Hi Marco,
<>> <>
<>> <>> -----Original Message-----
<>> <>> From: Marco Barcella [mailto:barcella@appiancorp.com]
<>> <>> Sent: 07 October 2002 20:14
<>> <>> To: Cactus Users List
<>> <>> Subject: Particular Configuration Problem
<>> <>>
<>> <>> Hi all,
<>> <>>
<>> <>> I understand that I am supposed to configure the server side
<>(web.xml)
<>> <>> and the client side (cactus.properties: contextURL).
<>> <>>
<>> <>> I am using TOMCAT 4.0.3
<>> <>>
<>> <>> In my case: I have an application that I deploy to C:/foe/bo/
<>> <>(deployed
<>> <>> application);
<>> <>> this application comes with a web.xml that I can modify adding the
<>> <>> redirectors definition, as specified by the website tutorial. If I
<>do
<>> <>that
<>> <>> everything works, but, ideally I should not modify that web.xml.
<>> <>Instead,
<>> <>> I should create another application (testing application) (in
<>webapps
<>> <>for
<>> <>> example) where I create
<>> <>> the web.xml which defines the redirectors (instead of modifying
<>the
<>> <>> deployed
<>> <>> application web.xml) and
<>> <>> place a build.xml that runs the tests through ANT.
<>> <>>
<>> <>
<>> <>Ideally, yes ... but not in the current cactus. The strategy is to
<>have
<>> <>ant scripts that create 2 wars : one for production and one for
<>testing.
<>> <>
<>> <>> THE PROBLEM is that in order to have the redirectors found, I have
<>to
<>> <>> specify the URLContext to be
<>> <>> the testing application URL. Therefore I cannot define the
<>URLContext
<>> <>to
<>> <>> be
<>> <>> the deployed application
<>> <>> one and therefore I cannot use some methods like
<>> <>> pageContext.include(relariveURL), testing some files in the
<>deployed
<>> <>> application.
<>> <>
<>> <>It won't work anyway as one webapp is completely separate from
<>another
<>> <>webapp. They live in different realms and cannot call each other. I
<>> <>think there is a JSR (or maybe it is the upcoming Servlet API 2.4 ?)
<>> <>that allows cross-webapp calls but it's definitely not in 2.2 nor
<>2.3.
<>> <>
<>> <>>
<>> <>> I could define the redirectors in the global web.xml, but I am
<>trying
<>> <>to
<>> <>> avoid that.
<>> <>> Am I missing something? Is there a way to do what I would like to
<>do?
<>> <>
<>> <>Yes, by having 2 web.xml and packaging 2 wars. BTW, if you're
<>concerned
<>> <>about reuse you can have only one web.xml which gets resolved
<>> <>differently if you're packaging the test war. See
<>> <>http://jakarta.apache.org/cactus/faq.html#faq2
<>> <>
<>> <>-Vincent
<>> <>
<>> <>>
<>> <>> Thanks in advance,
<>> <>> marco
<>> <>>
<>> <>>
<>> <>>
<>> <>>
<>> <>> --
<>> <>> To unsubscribe, e-mail: <mailto:cactus-user-
<>> <>> unsubscribe@jakarta.apache.org>
<>> <>> For additional commands, e-mail: <mailto:cactus-user-
<>> <>> help@jakarta.apache.org>
<>> <>
<>> <>
<>> <>
<>> <>--
<>> <>To unsubscribe, e-mail:
<>> <><...@jakarta.apache.org>
<>> <>For additional commands, e-mail:
<>> <><...@jakarta.apache.org>
<>> <>
<>> <>
<>>
<>> --
<>> To unsubscribe, e-mail: <mailto:cactus-user-
<>> unsubscribe@jakarta.apache.org>
<>> For additional commands, e-mail: <mailto:cactus-user-
<>> help@jakarta.apache.org>
<>
<>
<>
<>--
<>To unsubscribe, e-mail:
<><...@jakarta.apache.org>
<>For additional commands, e-mail:
<><...@jakarta.apache.org>
<>
<>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Particular Configuration Problem
Posted by Vincent Massol <vm...@octo.com>.
> -----Original Message-----
> From: Marco Barcella [mailto:barcella@appiancorp.com]
> Sent: 07 October 2002 21:48
> To: Cactus Users List
> Subject: RE: Particular Configuration Problem
>
> Thanks Vincent,
>
> let me make sure I understand one last point:
> I should be able to add the redirector definitions
> to the global web.xml in TOMCAT and avoid modifying
> the production web.xml. Right? So far it seems to work
> but not sure about the future.
Yes, that does work (and it's quite neat!) because Tomcat does a "merge"
of both web.xml. It's a Tomcat specific feature and won't work for all
servlet containers.
-Vincent
>
> Thanks a lot for the advices,
> marco
>
> <>-----Original Message-----
> <>From: Vincent Massol [mailto:vmassol@octo.com]
> <>Sent: Monday, October 07, 2002 4:11 PM
> <>To: 'Cactus Users List'
> <>Subject: RE: Particular Configuration Problem
> <>
> <>
> <>Hi Marco,
> <>
> <>> -----Original Message-----
> <>> From: Marco Barcella [mailto:barcella@appiancorp.com]
> <>> Sent: 07 October 2002 20:14
> <>> To: Cactus Users List
> <>> Subject: Particular Configuration Problem
> <>>
> <>> Hi all,
> <>>
> <>> I understand that I am supposed to configure the server side
(web.xml)
> <>> and the client side (cactus.properties: contextURL).
> <>>
> <>> I am using TOMCAT 4.0.3
> <>>
> <>> In my case: I have an application that I deploy to C:/foe/bo/
> <>(deployed
> <>> application);
> <>> this application comes with a web.xml that I can modify adding the
> <>> redirectors definition, as specified by the website tutorial. If I
do
> <>that
> <>> everything works, but, ideally I should not modify that web.xml.
> <>Instead,
> <>> I should create another application (testing application) (in
webapps
> <>for
> <>> example) where I create
> <>> the web.xml which defines the redirectors (instead of modifying
the
> <>> deployed
> <>> application web.xml) and
> <>> place a build.xml that runs the tests through ANT.
> <>>
> <>
> <>Ideally, yes ... but not in the current cactus. The strategy is to
have
> <>ant scripts that create 2 wars : one for production and one for
testing.
> <>
> <>> THE PROBLEM is that in order to have the redirectors found, I have
to
> <>> specify the URLContext to be
> <>> the testing application URL. Therefore I cannot define the
URLContext
> <>to
> <>> be
> <>> the deployed application
> <>> one and therefore I cannot use some methods like
> <>> pageContext.include(relariveURL), testing some files in the
deployed
> <>> application.
> <>
> <>It won't work anyway as one webapp is completely separate from
another
> <>webapp. They live in different realms and cannot call each other. I
> <>think there is a JSR (or maybe it is the upcoming Servlet API 2.4 ?)
> <>that allows cross-webapp calls but it's definitely not in 2.2 nor
2.3.
> <>
> <>>
> <>> I could define the redirectors in the global web.xml, but I am
trying
> <>to
> <>> avoid that.
> <>> Am I missing something? Is there a way to do what I would like to
do?
> <>
> <>Yes, by having 2 web.xml and packaging 2 wars. BTW, if you're
concerned
> <>about reuse you can have only one web.xml which gets resolved
> <>differently if you're packaging the test war. See
> <>http://jakarta.apache.org/cactus/faq.html#faq2
> <>
> <>-Vincent
> <>
> <>>
> <>> Thanks in advance,
> <>> marco
> <>>
> <>>
> <>>
> <>>
> <>> --
> <>> To unsubscribe, e-mail: <mailto:cactus-user-
> <>> unsubscribe@jakarta.apache.org>
> <>> For additional commands, e-mail: <mailto:cactus-user-
> <>> help@jakarta.apache.org>
> <>
> <>
> <>
> <>--
> <>To unsubscribe, e-mail:
> <><...@jakarta.apache.org>
> <>For additional commands, e-mail:
> <><...@jakarta.apache.org>
> <>
> <>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Particular Configuration Problem
Posted by Marco Barcella <ba...@appiancorp.com>.
Thanks Vincent,
let me make sure I understand one last point:
I should be able to add the redirector definitions
to the global web.xml in TOMCAT and avoid modifying
the production web.xml. Right? So far it seems to work
but not sure about the future.
Thanks a lot for the advices,
marco
<>-----Original Message-----
<>From: Vincent Massol [mailto:vmassol@octo.com]
<>Sent: Monday, October 07, 2002 4:11 PM
<>To: 'Cactus Users List'
<>Subject: RE: Particular Configuration Problem
<>
<>
<>Hi Marco,
<>
<>> -----Original Message-----
<>> From: Marco Barcella [mailto:barcella@appiancorp.com]
<>> Sent: 07 October 2002 20:14
<>> To: Cactus Users List
<>> Subject: Particular Configuration Problem
<>>
<>> Hi all,
<>>
<>> I understand that I am supposed to configure the server side (web.xml)
<>> and the client side (cactus.properties: contextURL).
<>>
<>> I am using TOMCAT 4.0.3
<>>
<>> In my case: I have an application that I deploy to C:/foe/bo/
<>(deployed
<>> application);
<>> this application comes with a web.xml that I can modify adding the
<>> redirectors definition, as specified by the website tutorial. If I do
<>that
<>> everything works, but, ideally I should not modify that web.xml.
<>Instead,
<>> I should create another application (testing application) (in webapps
<>for
<>> example) where I create
<>> the web.xml which defines the redirectors (instead of modifying the
<>> deployed
<>> application web.xml) and
<>> place a build.xml that runs the tests through ANT.
<>>
<>
<>Ideally, yes ... but not in the current cactus. The strategy is to have
<>ant scripts that create 2 wars : one for production and one for testing.
<>
<>> THE PROBLEM is that in order to have the redirectors found, I have to
<>> specify the URLContext to be
<>> the testing application URL. Therefore I cannot define the URLContext
<>to
<>> be
<>> the deployed application
<>> one and therefore I cannot use some methods like
<>> pageContext.include(relariveURL), testing some files in the deployed
<>> application.
<>
<>It won't work anyway as one webapp is completely separate from another
<>webapp. They live in different realms and cannot call each other. I
<>think there is a JSR (or maybe it is the upcoming Servlet API 2.4 ?)
<>that allows cross-webapp calls but it's definitely not in 2.2 nor 2.3.
<>
<>>
<>> I could define the redirectors in the global web.xml, but I am trying
<>to
<>> avoid that.
<>> Am I missing something? Is there a way to do what I would like to do?
<>
<>Yes, by having 2 web.xml and packaging 2 wars. BTW, if you're concerned
<>about reuse you can have only one web.xml which gets resolved
<>differently if you're packaging the test war. See
<>http://jakarta.apache.org/cactus/faq.html#faq2
<>
<>-Vincent
<>
<>>
<>> Thanks in advance,
<>> marco
<>>
<>>
<>>
<>>
<>> --
<>> To unsubscribe, e-mail: <mailto:cactus-user-
<>> unsubscribe@jakarta.apache.org>
<>> For additional commands, e-mail: <mailto:cactus-user-
<>> help@jakarta.apache.org>
<>
<>
<>
<>--
<>To unsubscribe, e-mail:
<><...@jakarta.apache.org>
<>For additional commands, e-mail:
<><...@jakarta.apache.org>
<>
<>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Particular Configuration Problem
Posted by Vincent Massol <vm...@octo.com>.
Hi Marco,
> -----Original Message-----
> From: Marco Barcella [mailto:barcella@appiancorp.com]
> Sent: 07 October 2002 20:14
> To: Cactus Users List
> Subject: Particular Configuration Problem
>
> Hi all,
>
> I understand that I am supposed to configure the server side (web.xml)
> and the client side (cactus.properties: contextURL).
>
> I am using TOMCAT 4.0.3
>
> In my case: I have an application that I deploy to C:/foe/bo/
(deployed
> application);
> this application comes with a web.xml that I can modify adding the
> redirectors definition, as specified by the website tutorial. If I do
that
> everything works, but, ideally I should not modify that web.xml.
Instead,
> I should create another application (testing application) (in webapps
for
> example) where I create
> the web.xml which defines the redirectors (instead of modifying the
> deployed
> application web.xml) and
> place a build.xml that runs the tests through ANT.
>
Ideally, yes ... but not in the current cactus. The strategy is to have
ant scripts that create 2 wars : one for production and one for testing.
> THE PROBLEM is that in order to have the redirectors found, I have to
> specify the URLContext to be
> the testing application URL. Therefore I cannot define the URLContext
to
> be
> the deployed application
> one and therefore I cannot use some methods like
> pageContext.include(relariveURL), testing some files in the deployed
> application.
It won't work anyway as one webapp is completely separate from another
webapp. They live in different realms and cannot call each other. I
think there is a JSR (or maybe it is the upcoming Servlet API 2.4 ?)
that allows cross-webapp calls but it's definitely not in 2.2 nor 2.3.
>
> I could define the redirectors in the global web.xml, but I am trying
to
> avoid that.
> Am I missing something? Is there a way to do what I would like to do?
Yes, by having 2 web.xml and packaging 2 wars. BTW, if you're concerned
about reuse you can have only one web.xml which gets resolved
differently if you're packaging the test war. See
http://jakarta.apache.org/cactus/faq.html#faq2
-Vincent
>
> Thanks in advance,
> marco
>
>
>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Particular Configuration Problem
Posted by Marco Barcella <ba...@appiancorp.com>.
Hi all,
I understand that I am supposed to configure the server side (web.xml)
and the client side (cactus.properties: contextURL).
I am using TOMCAT 4.0.3
In my case: I have an application that I deploy to C:/foe/bo/ (deployed
application);
this application comes with a web.xml that I can modify adding the
redirectors definition, as specified by the website tutorial. If I do that
everything works, but, ideally I should not modify that web.xml. Instead,
I should create another application (testing application) (in webapps for
example) where I create
the web.xml which defines the redirectors (instead of modifying the deployed
application web.xml) and
place a build.xml that runs the tests through ANT.
THE PROBLEM is that in order to have the redirectors found, I have to
specify the URLContext to be
the testing application URL. Therefore I cannot define the URLContext to be
the deployed application
one and therefore I cannot use some methods like
pageContext.include(relariveURL), testing some files in the deployed
application.
I could define the redirectors in the global web.xml, but I am trying to
avoid that.
Am I missing something? Is there a way to do what I would like to do?
Thanks in advance,
marco
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Method not found
Posted by Peter Neubauer <pe...@yahoo.se>.
fre 2002-10-11 klockan 19.16 skrev Nicholas Lesiecki:
> It looks like you may be using an incompatible version of the httpclient
> JAR. Can you check that possibility?
I changed jars forth and back, and finally got it working using commons-httpclient-2.0-dev.jar
Anyways, the methods are in the 1.0 versions too, but I still don't know
why I get the error using them.
Thanks for the help!
/peter
>
> Cheers,
> Nick
>
> > -----Original Message-----
> > From: Peter Neubauer [mailto:peter_neubauer2001@yahoo.se]
> > Sent: Thursday, October 10, 2002 10:45 PM
> > To: 'Cactus Users List'
> > Subject: Method not found
> >
> >
> > Hi,
> > running cactus I get the following:
> > 345 [main] DEBUG test.TurbineTest - Exception in test
> > java.lang.NoSuchMethodError:
> > org.apache.commons.httpclient.methods.GetMethod.setRequestHeader(L
> > java/lang/String;Ljava/lang/String;)V
> > at
> > org.apache.cactus.client.HttpClientConnectionHelper.dispatch24_con
> > nect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/Lo
> > gAspect.aj(1k):142)
> > at
> > org.apache.cactus.client.HttpClientConnectionHelper.around24_conne
> > ct(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogA
> > spect.aj(1k):1218)
> > at
> > org.apache.cactus.client.HttpClientConnectionHelper.connect(HttpCl
> ientConnectionHelper.java;org/apache/cactus/util/log/LogAspect.aj(1k):106)
> > at
> > org.apache.cactus.client.AbstractHttpClient.callRunTest(AbstractHt
> tpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):186)
> > at
> > org.apache.cactus.client.AbstractHttpClient.dispatch2_doTest(Abstr
> actHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):109)
> > at
> > org.apache.cactus.client.AbstractHttpClient.around2_doTest(Abstrac
> tHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):1218)
> > at
> > org.apache.cactus.client.AbstractHttpClient.doTest(AbstractHttpCli
> ent.java;org/apache/cactus/util/log/LogAspect.aj(1k):104)
> > at
> > org.apache.cactus.AbstractWebTestCase.runGenericTest(AbstractWebTe
> > stCase.java:260)
> > at
> > org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:133)
> >
> > I'm running with cactus-13-1.4.1 and commons-httpclient-2.0-dev.har.
> > Is it necessary to have these jars in the servers commons/lib path or is
> > it sufficient for them just to be in WEB-INF/lib/? Right now they are
> > just in the webapp.
> >
> > Has anyone seen this before?
> >
> > /peter
> >
> > _____________________________________________________
> > Gratis e-mail resten av livet på www.yahoo.se/mail
> > Busenkelt!
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
_____________________________________________________
Följ VM på nära håll på Yahoo!s officielle VM-sajt www.yahoo.se/vm2002
Håll dig ajour med nyheter och resultat, med vinnare och förlorare...
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Posted by Vincent Massol <vm...@octo.com>.
Marco,
> -----Original Message-----
> From: Marco Barcella [mailto:barcella@appiancorp.com]
> Sent: 15 October 2002 17:13
> To: Cactus Users List
> Subject: RE: java.lang.ClassCastException:
> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
>
> Thanks Vincent,
>
> 1/ Tomcat 4.0.3
ok. That should work just fine as it works for me.
> 2/ I have .jar in three places:
> tomcat/common/lib:
> aspectjrt-1.0.5.jar
> cactus-1.4.1.jar
> cactus-ant-1.4.1.jar
> commons-httpclient-2.0alpha1-200206
> commons-logging.jar
> httpunit-1.4.1.jar
> junit.jar
> servletapi-2.3.jar
> Tidy.jar
> xerces.jar
> xml-apis.jar
>
ok
> [testingdirectory]/WEB-INF/lib:
> aspectjrt-1.0.5.jar
> cactus-1.4.1.jar
> cactus-ant-1.4.1.jar
> commons-httpclient-2.0alpha1-200206
> commons-logging.jar
> httpunit-1.4.1.jar
> junit.jar
> servletapi-2.3.jar
> Tidy.jar
> xerces.jar
> xml-apis.jar
>
> the [testingdirectory] only contains the build.xml
> and it has to contain the .jar files even if they are in the
> tomcat/common/lib (it is not very clear to me why this is necessary
> as I don't refer to this lib in my build.xml)
Do you mean this is from where you start the tests? I guess I am
confused by the WEB-INF/ directory which would indicate a webapp. But
reading between the lines, I gather you use Ant to start your tests
using the junit ant task in which you add all the mentioned jars to be
put in junit task classpath.
>
> [applicationtotest]/WEB-INF/lib:
> ([applicationtotest]/WEB-INF/classes contains the classes to test and
the
> testing classes I write)
> appian-asl.jar
> appian-client.jar
> classes12.jar
> commons-beanutils.jar
> commons-collections.jar
> commons-digester.jar
> commons-pool.jar
> commons-loggin.jar
> cos.jar
> i18n.jar
> jakarta-poi-1.5.1-final-2002061
> JTurbo.jar
> log4j-1.2.6.jar
> struts.jar
> xalan.jar
> xalanservlet.jar
> xercesImpl.jar
> xml-apis.jar
What's the version of commons-logging.jar in your webapp? Is it the same
as the cactus one?
I have to say I don't know what's happening. I think your best bet might
be to ask the commons-dev mailing list (where commons-logging is).
Alternatively if you could send me a minimal zip still showing the
error, I could try to debug it.
>
> Now, the PROBLEM DISAPPEARS WHEN I remove the commons-loggin.jar,
you mean remove the one in your webapp?
> but
> this is not an option for me. I hope I was clear enough.
> Thanks!!!
> marco
>
-Vincent
[snip]
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Posted by Marco Barcella <ba...@appiancorp.com>.
Thanks Vincent,
1/ Tomcat 4.0.3
2/ I have .jar in three places:
tomcat/common/lib:
aspectjrt-1.0.5.jar
cactus-1.4.1.jar
cactus-ant-1.4.1.jar
commons-httpclient-2.0alpha1-200206
commons-logging.jar
httpunit-1.4.1.jar
junit.jar
servletapi-2.3.jar
Tidy.jar
xerces.jar
xml-apis.jar
[testingdirectory]/WEB-INF/lib:
aspectjrt-1.0.5.jar
cactus-1.4.1.jar
cactus-ant-1.4.1.jar
commons-httpclient-2.0alpha1-200206
commons-logging.jar
httpunit-1.4.1.jar
junit.jar
servletapi-2.3.jar
Tidy.jar
xerces.jar
xml-apis.jar
the [testingdirectory] only contains the build.xml
and it has to contain the .jar files even if they are in the
tomcat/common/lib (it is not very clear to me why this is necessary
as I don't refer to this lib in my build.xml)
[applicationtotest]/WEB-INF/lib:
([applicationtotest]/WEB-INF/classes contains the classes to test and the
testing classes I write)
appian-asl.jar
appian-client.jar
classes12.jar
commons-beanutils.jar
commons-collections.jar
commons-digester.jar
commons-pool.jar
commons-loggin.jar
cos.jar
i18n.jar
jakarta-poi-1.5.1-final-2002061
JTurbo.jar
log4j-1.2.6.jar
struts.jar
xalan.jar
xalanservlet.jar
xercesImpl.jar
xml-apis.jar
Now, the PROBLEM DISAPPEARS WHEN I remove the commons-loggin.jar, but
this is not an option for me. I hope I was clear enough.
Thanks!!!
marco
<>-----Original Message-----
<>From: Vincent Massol [mailto:vmassol@octo.com]
<>Sent: Tuesday, October 15, 2002 5:50 AM
<>To: 'Cactus Users List'
<>Subject: RE: java.lang.ClassCastException:
<>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>
<>
<>Marco,
<>
<>1/ What version of Tomcat are you using?
<>2/ Where are all your jars located? In tomcat/common/lib? Do you have
<>jars in your webapp WEB-INF/lib directory? If so, which ones?
<>
<>Thanks
<>-Vincent
<>
<>> -----Original Message-----
<>> From: Marco Barcella [mailto:barcella@appiancorp.com]
<>> Sent: 14 October 2002 17:06
<>> To: Cactus Users List
<>> Subject: RE: java.lang.ClassCastException:
<>> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>>
<>> Thanks again,
<>>
<>> unfortunately I have the same problem.
<>> Maybe I am missing some other detail ?
<>> Any idea would be very welcome,
<>> thanks,
<>> marco
<>>
<>> <>-----Original Message-----
<>> <>From: Larry Tambascio [mailto:ltambascio@charter.net]
<>> <>Sent: Sunday, October 13, 2002 9:58 PM
<>> <>To: 'Cactus Users List'
<>> <>Subject: RE: java.lang.ClassCastException:
<>> <>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>> <>
<>> <>
<>> <>Hi Marco,
<>> <>
<>> <>In your original message, you said that you had the
<>commons-logging.jar
<>> in
<>> <>front of the log4j.jar file. I presume you meant in terms of order.
<>> <>
<>> <>In my environment, I have the log4j.jar file ahead of commons-
<>> logging.jar.
<>> <>Could it be that simple?? I noticed in the classpath "how to" on
<>> <>the cactus
<>> <>web site that log4j is listed after commons-logging. Not sure if
<>that's
<>> <>intentional.
<>> <>
<>> <>Try moving the commons-logging.jar file after the log4j.jar file in
<>your
<>> <>classpath. See if that works, and let's hope there's no strange
<>> <>compatibility issue between the commons-logging your project is
<>using
<>> and
<>> <>the one distributed with cactus.
<>> <>
<>> <>Later,
<>> <>-Larry
<>> <>
<>> <>-----Original Message-----
<>> <>From: Marco Barcella [mailto:barcella@appiancorp.com]
<>> <>Sent: Sunday, October 13, 2002 2:35 PM
<>> <>To: Cactus Users List
<>> <>Subject: RE: java.lang.ClassCastException:
<>> <>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>> <>
<>> <>
<>> <>Thanks,
<>> <>
<>> <>I got the new 4.1 .jar files and replaced the 1.4 ones
<>> <>in my tomcat/common/lib directory and in the application
<>> <>lib. I still get the same exception. Any new thoughts?
<>> <>thanks,
<>> <>marco
<>> <>
<>> <><>-----Original Message-----
<>> <><>From: Vincent Massol [mailto:vmassol@octo.com]
<>> <><>Sent: Saturday, October 12, 2002 3:59 PM
<>> <><>To: 'Cactus Users List'
<>> <><>Subject: RE: java.lang.ClassCastException:
<>> <><>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>> <><>
<>> <><>
<>> <><>Hi Marco,
<>> <><>
<>> <><>Which version of Cactus are you running? I seem to remember there
<>was
<>> an
<>> <><>issue with Cactus 1.4 that was fixed in 1.4.1 WRT to a commons
<>logging
<>> <><>class cast exception. Could that be it?
<>> <><>
<>> <><>-Vincent
<>> <><>
<>> <><>> -----Original Message-----
<>> <><>> From: Marco Barcella [mailto:barcella@appiancorp.com]
<>> <><>> Sent: 11 October 2002 19:12
<>> <><>> To: Cactus Users List
<>> <><>> Subject: java.lang.ClassCastException:
<>> <><>> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>> <><>>
<>> <><>> Hi,
<>> <><>>
<>> <><>> I had everything running then the application I am testing added
<>> <><>> commons-logging.jar
<>> <><>> on top of
<>> <><>> log4j-1.2.6.jar
<>> <><>> I get:
<>> <><>> java.lang.ClassCastException:
<>> <><>> org.apache.commons.logging.impl.LogFactoryImpl
<>> <><>>
<>> <><>> I read that I should exclude the package from junit view, so I
<>added
<>> <><>to
<>> <><>> excluded.properties in junit-3.7.jar the following:
<>> <><>>
<>> <><>> excluded.6=org.apache.commons.logging.*
<>> <><>> excluded.7=org.apache.commons.logging.LogFactory.*
<>> <><>>
<>> <><>> I renamed the file to junit.jar and I replaced junit-3.7.jar
<>> <><>everywhere:
<>> <><>> tomcat/common/lib
<>> <><>> tomcat-ant/lib
<>> <><>> application/lib
<>> <><>>
<>> <><>> I still get the same error!!
<>> <><>>
<>> <><>> What am I doing wrong, should I do something else?
<>> <><>>
<>> <><>> Thanks a lot in advance,
<>> <><>> marco
<>> <><>>
<>
<>[snip]
<>
<>
<>--
<>To unsubscribe, e-mail:
<><...@jakarta.apache.org>
<>For additional commands, e-mail:
<><...@jakarta.apache.org>
<>
<>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Posted by Vincent Massol <vm...@octo.com>.
Marco,
1/ What version of Tomcat are you using?
2/ Where are all your jars located? In tomcat/common/lib? Do you have
jars in your webapp WEB-INF/lib directory? If so, which ones?
Thanks
-Vincent
> -----Original Message-----
> From: Marco Barcella [mailto:barcella@appiancorp.com]
> Sent: 14 October 2002 17:06
> To: Cactus Users List
> Subject: RE: java.lang.ClassCastException:
> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
>
> Thanks again,
>
> unfortunately I have the same problem.
> Maybe I am missing some other detail ?
> Any idea would be very welcome,
> thanks,
> marco
>
> <>-----Original Message-----
> <>From: Larry Tambascio [mailto:ltambascio@charter.net]
> <>Sent: Sunday, October 13, 2002 9:58 PM
> <>To: 'Cactus Users List'
> <>Subject: RE: java.lang.ClassCastException:
> <>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
> <>
> <>
> <>Hi Marco,
> <>
> <>In your original message, you said that you had the
commons-logging.jar
> in
> <>front of the log4j.jar file. I presume you meant in terms of order.
> <>
> <>In my environment, I have the log4j.jar file ahead of commons-
> logging.jar.
> <>Could it be that simple?? I noticed in the classpath "how to" on
> <>the cactus
> <>web site that log4j is listed after commons-logging. Not sure if
that's
> <>intentional.
> <>
> <>Try moving the commons-logging.jar file after the log4j.jar file in
your
> <>classpath. See if that works, and let's hope there's no strange
> <>compatibility issue between the commons-logging your project is
using
> and
> <>the one distributed with cactus.
> <>
> <>Later,
> <>-Larry
> <>
> <>-----Original Message-----
> <>From: Marco Barcella [mailto:barcella@appiancorp.com]
> <>Sent: Sunday, October 13, 2002 2:35 PM
> <>To: Cactus Users List
> <>Subject: RE: java.lang.ClassCastException:
> <>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
> <>
> <>
> <>Thanks,
> <>
> <>I got the new 4.1 .jar files and replaced the 1.4 ones
> <>in my tomcat/common/lib directory and in the application
> <>lib. I still get the same exception. Any new thoughts?
> <>thanks,
> <>marco
> <>
> <><>-----Original Message-----
> <><>From: Vincent Massol [mailto:vmassol@octo.com]
> <><>Sent: Saturday, October 12, 2002 3:59 PM
> <><>To: 'Cactus Users List'
> <><>Subject: RE: java.lang.ClassCastException:
> <><>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
> <><>
> <><>
> <><>Hi Marco,
> <><>
> <><>Which version of Cactus are you running? I seem to remember there
was
> an
> <><>issue with Cactus 1.4 that was fixed in 1.4.1 WRT to a commons
logging
> <><>class cast exception. Could that be it?
> <><>
> <><>-Vincent
> <><>
> <><>> -----Original Message-----
> <><>> From: Marco Barcella [mailto:barcella@appiancorp.com]
> <><>> Sent: 11 October 2002 19:12
> <><>> To: Cactus Users List
> <><>> Subject: java.lang.ClassCastException:
> <><>> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
> <><>>
> <><>> Hi,
> <><>>
> <><>> I had everything running then the application I am testing added
> <><>> commons-logging.jar
> <><>> on top of
> <><>> log4j-1.2.6.jar
> <><>> I get:
> <><>> java.lang.ClassCastException:
> <><>> org.apache.commons.logging.impl.LogFactoryImpl
> <><>>
> <><>> I read that I should exclude the package from junit view, so I
added
> <><>to
> <><>> excluded.properties in junit-3.7.jar the following:
> <><>>
> <><>> excluded.6=org.apache.commons.logging.*
> <><>> excluded.7=org.apache.commons.logging.LogFactory.*
> <><>>
> <><>> I renamed the file to junit.jar and I replaced junit-3.7.jar
> <><>everywhere:
> <><>> tomcat/common/lib
> <><>> tomcat-ant/lib
> <><>> application/lib
> <><>>
> <><>> I still get the same error!!
> <><>>
> <><>> What am I doing wrong, should I do something else?
> <><>>
> <><>> Thanks a lot in advance,
> <><>> marco
> <><>>
[snip]
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Posted by Marco Barcella <ba...@appiancorp.com>.
Thanks again,
unfortunately I have the same problem.
Maybe I am missing some other detail ?
Any idea would be very welcome,
thanks,
marco
<>-----Original Message-----
<>From: Larry Tambascio [mailto:ltambascio@charter.net]
<>Sent: Sunday, October 13, 2002 9:58 PM
<>To: 'Cactus Users List'
<>Subject: RE: java.lang.ClassCastException:
<>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>
<>
<>Hi Marco,
<>
<>In your original message, you said that you had the commons-logging.jar in
<>front of the log4j.jar file. I presume you meant in terms of order.
<>
<>In my environment, I have the log4j.jar file ahead of commons-logging.jar.
<>Could it be that simple?? I noticed in the classpath "how to" on
<>the cactus
<>web site that log4j is listed after commons-logging. Not sure if that's
<>intentional.
<>
<>Try moving the commons-logging.jar file after the log4j.jar file in your
<>classpath. See if that works, and let's hope there's no strange
<>compatibility issue between the commons-logging your project is using and
<>the one distributed with cactus.
<>
<>Later,
<>-Larry
<>
<>-----Original Message-----
<>From: Marco Barcella [mailto:barcella@appiancorp.com]
<>Sent: Sunday, October 13, 2002 2:35 PM
<>To: Cactus Users List
<>Subject: RE: java.lang.ClassCastException:
<>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>
<>
<>Thanks,
<>
<>I got the new 4.1 .jar files and replaced the 1.4 ones
<>in my tomcat/common/lib directory and in the application
<>lib. I still get the same exception. Any new thoughts?
<>thanks,
<>marco
<>
<><>-----Original Message-----
<><>From: Vincent Massol [mailto:vmassol@octo.com]
<><>Sent: Saturday, October 12, 2002 3:59 PM
<><>To: 'Cactus Users List'
<><>Subject: RE: java.lang.ClassCastException:
<><>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<><>
<><>
<><>Hi Marco,
<><>
<><>Which version of Cactus are you running? I seem to remember there was an
<><>issue with Cactus 1.4 that was fixed in 1.4.1 WRT to a commons logging
<><>class cast exception. Could that be it?
<><>
<><>-Vincent
<><>
<><>> -----Original Message-----
<><>> From: Marco Barcella [mailto:barcella@appiancorp.com]
<><>> Sent: 11 October 2002 19:12
<><>> To: Cactus Users List
<><>> Subject: java.lang.ClassCastException:
<><>> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<><>>
<><>> Hi,
<><>>
<><>> I had everything running then the application I am testing added
<><>> commons-logging.jar
<><>> on top of
<><>> log4j-1.2.6.jar
<><>> I get:
<><>> java.lang.ClassCastException:
<><>> org.apache.commons.logging.impl.LogFactoryImpl
<><>>
<><>> I read that I should exclude the package from junit view, so I added
<><>to
<><>> excluded.properties in junit-3.7.jar the following:
<><>>
<><>> excluded.6=org.apache.commons.logging.*
<><>> excluded.7=org.apache.commons.logging.LogFactory.*
<><>>
<><>> I renamed the file to junit.jar and I replaced junit-3.7.jar
<><>everywhere:
<><>> tomcat/common/lib
<><>> tomcat-ant/lib
<><>> application/lib
<><>>
<><>> I still get the same error!!
<><>>
<><>> What am I doing wrong, should I do something else?
<><>>
<><>> Thanks a lot in advance,
<><>> marco
<><>>
<><>>
<><>> --
<><>> To unsubscribe, e-mail: <mailto:cactus-user-
<><>> unsubscribe@jakarta.apache.org>
<><>> For additional commands, e-mail: <mailto:cactus-user-
<><>> help@jakarta.apache.org>
<><>
<><>
<><>
<><>--
<><>To unsubscribe, e-mail:
<><...@jakarta.apache.org>
<><>For additional commands, e-mail:
<><...@jakarta.apache.org>
<><>
<><>
<>
<>--
<>To unsubscribe, e-mail:
<><...@jakarta.apache.org>
<>For additional commands, e-mail:
<><...@jakarta.apache.org>
<>
<>
<>--
<>To unsubscribe, e-mail:
<><...@jakarta.apache.org>
<>For additional commands, e-mail:
<><...@jakarta.apache.org>
<>
<>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Posted by Larry Tambascio <lt...@charter.net>.
Hi Marco,
In your original message, you said that you had the commons-logging.jar in
front of the log4j.jar file. I presume you meant in terms of order.
In my environment, I have the log4j.jar file ahead of commons-logging.jar.
Could it be that simple?? I noticed in the classpath "how to" on the cactus
web site that log4j is listed after commons-logging. Not sure if that's
intentional.
Try moving the commons-logging.jar file after the log4j.jar file in your
classpath. See if that works, and let's hope there's no strange
compatibility issue between the commons-logging your project is using and
the one distributed with cactus.
Later,
-Larry
-----Original Message-----
From: Marco Barcella [mailto:barcella@appiancorp.com]
Sent: Sunday, October 13, 2002 2:35 PM
To: Cactus Users List
Subject: RE: java.lang.ClassCastException:
org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Thanks,
I got the new 4.1 .jar files and replaced the 1.4 ones
in my tomcat/common/lib directory and in the application
lib. I still get the same exception. Any new thoughts?
thanks,
marco
<>-----Original Message-----
<>From: Vincent Massol [mailto:vmassol@octo.com]
<>Sent: Saturday, October 12, 2002 3:59 PM
<>To: 'Cactus Users List'
<>Subject: RE: java.lang.ClassCastException:
<>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>
<>
<>Hi Marco,
<>
<>Which version of Cactus are you running? I seem to remember there was an
<>issue with Cactus 1.4 that was fixed in 1.4.1 WRT to a commons logging
<>class cast exception. Could that be it?
<>
<>-Vincent
<>
<>> -----Original Message-----
<>> From: Marco Barcella [mailto:barcella@appiancorp.com]
<>> Sent: 11 October 2002 19:12
<>> To: Cactus Users List
<>> Subject: java.lang.ClassCastException:
<>> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>>
<>> Hi,
<>>
<>> I had everything running then the application I am testing added
<>> commons-logging.jar
<>> on top of
<>> log4j-1.2.6.jar
<>> I get:
<>> java.lang.ClassCastException:
<>> org.apache.commons.logging.impl.LogFactoryImpl
<>>
<>> I read that I should exclude the package from junit view, so I added
<>to
<>> excluded.properties in junit-3.7.jar the following:
<>>
<>> excluded.6=org.apache.commons.logging.*
<>> excluded.7=org.apache.commons.logging.LogFactory.*
<>>
<>> I renamed the file to junit.jar and I replaced junit-3.7.jar
<>everywhere:
<>> tomcat/common/lib
<>> tomcat-ant/lib
<>> application/lib
<>>
<>> I still get the same error!!
<>>
<>> What am I doing wrong, should I do something else?
<>>
<>> Thanks a lot in advance,
<>> marco
<>>
<>>
<>> --
<>> To unsubscribe, e-mail: <mailto:cactus-user-
<>> unsubscribe@jakarta.apache.org>
<>> For additional commands, e-mail: <mailto:cactus-user-
<>> help@jakarta.apache.org>
<>
<>
<>
<>--
<>To unsubscribe, e-mail:
<><...@jakarta.apache.org>
<>For additional commands, e-mail:
<><...@jakarta.apache.org>
<>
<>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Posted by Marco Barcella <ba...@appiancorp.com>.
Thanks,
I got the new 4.1 .jar files and replaced the 1.4 ones
in my tomcat/common/lib directory and in the application
lib. I still get the same exception. Any new thoughts?
thanks,
marco
<>-----Original Message-----
<>From: Vincent Massol [mailto:vmassol@octo.com]
<>Sent: Saturday, October 12, 2002 3:59 PM
<>To: 'Cactus Users List'
<>Subject: RE: java.lang.ClassCastException:
<>org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>
<>
<>Hi Marco,
<>
<>Which version of Cactus are you running? I seem to remember there was an
<>issue with Cactus 1.4 that was fixed in 1.4.1 WRT to a commons logging
<>class cast exception. Could that be it?
<>
<>-Vincent
<>
<>> -----Original Message-----
<>> From: Marco Barcella [mailto:barcella@appiancorp.com]
<>> Sent: 11 October 2002 19:12
<>> To: Cactus Users List
<>> Subject: java.lang.ClassCastException:
<>> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
<>>
<>> Hi,
<>>
<>> I had everything running then the application I am testing added
<>> commons-logging.jar
<>> on top of
<>> log4j-1.2.6.jar
<>> I get:
<>> java.lang.ClassCastException:
<>> org.apache.commons.logging.impl.LogFactoryImpl
<>>
<>> I read that I should exclude the package from junit view, so I added
<>to
<>> excluded.properties in junit-3.7.jar the following:
<>>
<>> excluded.6=org.apache.commons.logging.*
<>> excluded.7=org.apache.commons.logging.LogFactory.*
<>>
<>> I renamed the file to junit.jar and I replaced junit-3.7.jar
<>everywhere:
<>> tomcat/common/lib
<>> tomcat-ant/lib
<>> application/lib
<>>
<>> I still get the same error!!
<>>
<>> What am I doing wrong, should I do something else?
<>>
<>> Thanks a lot in advance,
<>> marco
<>>
<>>
<>> --
<>> To unsubscribe, e-mail: <mailto:cactus-user-
<>> unsubscribe@jakarta.apache.org>
<>> For additional commands, e-mail: <mailto:cactus-user-
<>> help@jakarta.apache.org>
<>
<>
<>
<>--
<>To unsubscribe, e-mail:
<><...@jakarta.apache.org>
<>For additional commands, e-mail:
<><...@jakarta.apache.org>
<>
<>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Posted by Vincent Massol <vm...@octo.com>.
Hi Marco,
Which version of Cactus are you running? I seem to remember there was an
issue with Cactus 1.4 that was fixed in 1.4.1 WRT to a commons logging
class cast exception. Could that be it?
-Vincent
> -----Original Message-----
> From: Marco Barcella [mailto:barcella@appiancorp.com]
> Sent: 11 October 2002 19:12
> To: Cactus Users List
> Subject: java.lang.ClassCastException:
> org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
>
> Hi,
>
> I had everything running then the application I am testing added
> commons-logging.jar
> on top of
> log4j-1.2.6.jar
> I get:
> java.lang.ClassCastException:
> org.apache.commons.logging.impl.LogFactoryImpl
>
> I read that I should exclude the package from junit view, so I added
to
> excluded.properties in junit-3.7.jar the following:
>
> excluded.6=org.apache.commons.logging.*
> excluded.7=org.apache.commons.logging.LogFactory.*
>
> I renamed the file to junit.jar and I replaced junit-3.7.jar
everywhere:
> tomcat/common/lib
> tomcat-ant/lib
> application/lib
>
> I still get the same error!!
>
> What am I doing wrong, should I do something else?
>
> Thanks a lot in advance,
> marco
>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl: cannot fix it
Posted by Marco Barcella <ba...@appiancorp.com>.
Hi,
I had everything running then the application I am testing added
commons-logging.jar
on top of
log4j-1.2.6.jar
I get:
java.lang.ClassCastException: org.apache.commons.logging.impl.LogFactoryImpl
I read that I should exclude the package from junit view, so I added to
excluded.properties in junit-3.7.jar the following:
excluded.6=org.apache.commons.logging.*
excluded.7=org.apache.commons.logging.LogFactory.*
I renamed the file to junit.jar and I replaced junit-3.7.jar everywhere:
tomcat/common/lib
tomcat-ant/lib
application/lib
I still get the same error!!
What am I doing wrong, should I do something else?
Thanks a lot in advance,
marco
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Method not found
Posted by Nicholas Lesiecki <ni...@eblox.com>.
It looks like you may be using an incompatible version of the httpclient
JAR. Can you check that possibility?
Cheers,
Nick
> -----Original Message-----
> From: Peter Neubauer [mailto:peter_neubauer2001@yahoo.se]
> Sent: Thursday, October 10, 2002 10:45 PM
> To: 'Cactus Users List'
> Subject: Method not found
>
>
> Hi,
> running cactus I get the following:
> 345 [main] DEBUG test.TurbineTest - Exception in test
> java.lang.NoSuchMethodError:
> org.apache.commons.httpclient.methods.GetMethod.setRequestHeader(L
> java/lang/String;Ljava/lang/String;)V
> at
> org.apache.cactus.client.HttpClientConnectionHelper.dispatch24_con
> nect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/Lo
> gAspect.aj(1k):142)
> at
> org.apache.cactus.client.HttpClientConnectionHelper.around24_conne
> ct(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogA
> spect.aj(1k):1218)
> at
> org.apache.cactus.client.HttpClientConnectionHelper.connect(HttpCl
ientConnectionHelper.java;org/apache/cactus/util/log/LogAspect.aj(1k):106)
> at
> org.apache.cactus.client.AbstractHttpClient.callRunTest(AbstractHt
tpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):186)
> at
> org.apache.cactus.client.AbstractHttpClient.dispatch2_doTest(Abstr
actHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):109)
> at
> org.apache.cactus.client.AbstractHttpClient.around2_doTest(Abstrac
tHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):1218)
> at
> org.apache.cactus.client.AbstractHttpClient.doTest(AbstractHttpCli
ent.java;org/apache/cactus/util/log/LogAspect.aj(1k):104)
> at
> org.apache.cactus.AbstractWebTestCase.runGenericTest(AbstractWebTe
> stCase.java:260)
> at
> org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:133)
>
> I'm running with cactus-13-1.4.1 and commons-httpclient-2.0-dev.har.
> Is it necessary to have these jars in the servers commons/lib path or is
> it sufficient for them just to be in WEB-INF/lib/? Right now they are
> just in the webapp.
>
> Has anyone seen this before?
>
> /peter
>
> _____________________________________________________
> Gratis e-mail resten av livet på www.yahoo.se/mail
> Busenkelt!
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Method not found
Posted by Peter Neubauer <pe...@yahoo.se>.
Hi,
running cactus I get the following:
345 [main] DEBUG test.TurbineTest - Exception in test
java.lang.NoSuchMethodError:
org.apache.commons.httpclient.methods.GetMethod.setRequestHeader(Ljava/lang/String;Ljava/lang/String;)V
at
org.apache.cactus.client.HttpClientConnectionHelper.dispatch24_connect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogAspect.aj(1k):142)
at
org.apache.cactus.client.HttpClientConnectionHelper.around24_connect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogAspect.aj(1k):1218)
at
org.apache.cactus.client.HttpClientConnectionHelper.connect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogAspect.aj(1k):106)
at
org.apache.cactus.client.AbstractHttpClient.callRunTest(AbstractHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):186)
at
org.apache.cactus.client.AbstractHttpClient.dispatch2_doTest(AbstractHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):109)
at
org.apache.cactus.client.AbstractHttpClient.around2_doTest(AbstractHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):1218)
at
org.apache.cactus.client.AbstractHttpClient.doTest(AbstractHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):104)
at
org.apache.cactus.AbstractWebTestCase.runGenericTest(AbstractWebTestCase.java:260)
at org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:133)
I'm running with cactus-13-1.4.1 and commons-httpclient-2.0-dev.har.
Is it necessary to have these jars in the servers commons/lib path or is
it sufficient for them just to be in WEB-INF/lib/? Right now they are
just in the webapp.
Has anyone seen this before?
/peter
_____________________________________________________
Gratis e-mail resten av livet p� www.yahoo.se/mail
Busenkelt!
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: IFrames
Posted by Vincent Massol <vm...@octo.com>.
Hi Wolfgang,
I confirm that Cactus is the wrong tool! It only does unit testing
(white box testing) ATM with a little functional testing by the ability
to assert the response using HttpUnit for example.
I don't know of any tool but I am sure there are. You can also patch
HttpUnit to add support for IFrame or ask for this feature on the
HttpUnit SourceForge web site.
Cheers,
-Vincent
> -----Original Message-----
> From: Wolfgang Egger [mailto:wolfgang.egger@beaglesoft.biz]
> Sent: 07 October 2002 11:01
> To: cactus-user@jakarta.apache.org
> Subject: IFrames
>
> Servus all out there,
>
> I'm not sure if this is he right mailing-list, but perhaps you can
give
> me some hints, what resources I should look at to solve my problem.
>
> We build a website using IFrames. Now I have to write a test, that
> follows all links that are reachable from a given page a page. The
links
> that are inside of IFrames and the sources of the IFrames self, has to
> be followed too. I have tried httpUnit, but it doesn't recognize
> IFrames. I took a look at the cactus documentation, but it seems, that
> this is the wrong tool, too.
> Does everyone know any resources, where I can get an idea, how to test
> IFrames automatically?
>
> Have a nice and peacefully day
>
> Wolfgang
>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>