Hi Eric,

I'm glad you solved the problem!

WRT security information, it's a limitation: I knew there would be a
problem at some point... but I couldn't think of a good solution at that
time. Right now your solution makes sense to me. However, there is a
limitation: as a user you cannot choose authentication details
(authentication type: BASIC, Form-based and username/credentials, etc).
But I guess these are improvements to bring in the plugin later on. One
solution is to externalize this information as properties of the plugin.
For example:

maven.cactus.security.type = BASIC

Note: You were correct about the change needed (I've just committed it
now). 

Feel free to submit any patch to improve the security configuration.

Thanks
-Vincent

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 17 December 2002 19:04
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: Cactus Plugin working?
> 
> Vincent, thank you for trying it out..  Knowing it worked somewhere
put me
> on the trail to solving it!  I ended up looking in my repository, and
I
> had
> a stack of older velocity-dvsl.jars...  I deleted them, grabbed the
newest
> dvsl jar, plus the snapshot one, and it worked!  So it seems like it
was a
> classloader issue.  I guess, plugins just grab whaterver class is
> available,
> versus just a specific version?
> 
> So, I now have one of my three webapps working smoothly...  DBForms is
> going
> to be getting more cactus tests now!
> 
> But of course, solving one issue doesn't solve them all..  Not sure if
> this
> bug is a bug, or a limitation of the plugin.  I think the dvsl needs
to
> remove any existing security information...  In my web.xml I have this
> section:
> 
>  <!-- Define a Security Constraint on this Application -->
>   <security-constraint>
>         <web-resource-collection>
>                 <web-resource-name>Fortius</web-resource-name>
>                 <url-pattern>/*</url-pattern>
>         </web-resource-collection>
>         <auth-constraint>
>                 <role-name>kpuser</role-name>
>         </auth-constraint>
>     </security-constraint>
> 
>   <!-- Define the Login Configuration for this Application -->
>   <login-config>
>     <auth-method>BASIC</auth-method>
>     <realm-name>Fortius</realm-name>
>   </login-config>
> 
> 
> However, this causes the plugin to fail because of authentication
issues.
> I
> don't mind hacking a patch if you agree this is the issue.  Should the
> lines
> in the dvsl:
> 
>     $context.applyTemplates("security-constraint")
> 
>     $context.applyTemplates("security-role")
> 
> actually be there?
> 
> Or, do I need to have my production web.xml with my security, and
another
> cactus one?
> 
> Eric
> 
> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 17, 2002 5:59 AM
> To: 'Turbine Maven Developers List'
> Cc: [EMAIL PROTECTED]
> Subject: RE: Cactus Plugin working?
> 
> 
> Hi Eric,
> 
> I've tried your web.xml with the sample application (the one packaged
> inside the cactus plugin, in the sample/ directory) and it seems to
work
> (see attached web.xml which is generated by the plugin).
> 
> Could you try with the sample application and see if it works for you
> too?
> 
> Thanks
> -Vincent
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: 16 December 2002 16:08
> > To: [EMAIL PROTECTED]
> > Subject: RE: Cactus Plugin working?
> >
> > Making progress!  Actually, the war tasks seems to call java:compile
> which
> > does enough compilation.  I upgraded to Tomcat 4.1.16 thinking that
> was
> > the
> > issue, but it finally boiled down to my web.xml...
> >
> > If I provide a web.xml, then the merge seems to fail.  All I get is
my
> > original web.xml, without all the redirector stuff.  If I don't
> provide a
> > web.xml, then the default one with the plugin is used.  However,
that
> > means
> > any params I have are ignored.
> >
> > Here is my web.xml:
> >
> > <?xml version="1.0" encoding="ISO-8859-1"?>
> >
> > <!DOCTYPE web-app
> >     PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
> >     "http://java.sun.com/dtd/web-app_2_3.dtd";>
> >
> > <web-app>
> >
> >
> > <!--=========== DbForms Configuration Servlet ===========-->
> >     <servlet>
> >         <servlet-name>org.dbforms.ConfigServlet</servlet-name>
> >         <servlet-class>org.dbforms.ConfigServlet</servlet-class>
> >
> >         <!-- Uncomment to enable log4j configuration -->
> >         <init-param>
> >             <param-name>log4j.configuration</param-name>
> >
<param-value>/WEB-INF/conf/log4j.properties</param-value>
> >         </init-param>
> >
> >         <!-- control how much debugging is sent.  0 is none -->
> >         <init-param>
> >             <param-name>digesterDebugLevel</param-name>
> >             <param-value>3</param-value>
> >         </init-param>
> >         <init-param>
> >                 <param-name>dbformsConfig</param-name>
> >
<param-value>/WEB-INF/conf/dbforms-config.xml</param-
> > value>
> >         </init-param>
> >         <init-param>
> >             <param-name>dbformsErrors</param-name>
> >
> <param-value>/WEB-INF/conf/dbforms-errors.xml</param-value>
> >         </init-param>
> >         <init-param>
> >             <param-name>validation</param-name>
> >             <param-value>/WEB-INF/conf/validation.xml</param-value>
> >         </init-param>
> >         <init-param>
> >             <param-name>validator-rules</param-name>
> >
> <param-value>/WEB-INF/conf/validator-rules.xml</param-value>
> >         </init-param>
> >         <init-param>
> >             <param-name>resourceBundle</param-name>
> >             <param-value>ApplicationResources</param-value>
> >         </init-param>
> >
> >         <load-on-startup>1</load-on-startup>
> >     </servlet>
> >
> >     <!--=========== DbForms Controller Servlet ==============-->
> >     <servlet>
> >         <servlet-name>control</servlet-name>
> >         <servlet-class>org.dbforms.Controller</servlet-class>
> >         <load-on-startup>3</load-on-startup>
> >     </servlet>
> >
> >
> >
> >
> >
> > </web-app>
> >
> > Thanks,
> > Eric Pugh
> >
> >
> > -----Original Message-----
> > From: Jeffrey D. Brekke [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, December 16, 2002 9:01 AM
> > To: Turbine Maven Developers List
> > Subject: Re: Cactus Plugin working?
> >
> >
> >
> > Eric,
> >
> > I think you'll need a java:jar in there, war:webapp doesn't seem to
> depend
> > on java:jar.
> >
> > On Mon, 16 Dec 2002 [EMAIL PROTECTED] wrote:
> >
> > > Last week a post was made that the Cactus plugin was working.  I
> > downloaded
> > > CVS head this morning, and tried to run the cactus plugin against
> some
> > > cactus tests that had worked before (a couple weeks ago) with
Maven
> and
> > > Tomcat 4.1.12.  I am doing the:
> > >
> > >   maven clean war:webapp cactus:tests-tomcat-4x
> > >
> > > process, and everything seems to build appropriatly.
Unfortunantly,
> the
> > > plugin seems to start the background thread for tomcat, and then
sit
> > there
> > > forever, not doing anything.  The last couple lines are attached
> before.
> > > Are other people successfully using the Cactus plugin?
> > >
> > > I'm dying to start running my Cactus tests again!
> > >
> > > Eric
> > >
> > > project.props:
> > > #cactus settings.  Make sure to point to your Tomcat!
> > > maven.cactus.tomcat4x.home = c:/java/tomcat
> > > maven.cactus.src.dir = tests/test-cactus
> > > maven.cactus.test.reportsDirectory =
${maven.build.dir}/test-reports
> > >
> > > Last couple messages:
> > >     [java] WebappLoader[/test]: Deploy JAR
> > > /WEB-INF/lib/protomatter-1.1.8-pre5.jar to
> > > C:\java\dbforms\target\cactus\tomc
> > > at4x\webapps\test\WEB-INF\lib\protomatter-1.1.8-pre5.jar
> > >     [java] WebappLoader[/test]: Deploy JAR
/WEB-INF/lib/request.jar
> to
> > > C:\java\dbforms\target\cactus\tomcat4x\webapps\te
> > > st\WEB-INF\lib\request.jar
> > >     [java] WebappLoader[/test]: Deploy JAR
> /WEB-INF/lib/xerces-1.4.4.jar
> > to
> > > C:\java\dbforms\target\cactus\tomcat4x\webap
> > > ps\test\WEB-INF\lib\xerces-1.4.4.jar
> > >     [java] WebappLoader[/test]: Reloading checks are enabled for
> this
> > > Context
> > >     [java] ContextConfig[/test]: Configured an authenticator for
> method
> > > BASIC
> > >     [java] StandardManager[/test]: Seeding random number generator
> class
> > > java.security.SecureRandom
> > >     [java] StandardManager[/test]: Seeding of random number
> generator
> > has
> > > been completed
> > >     [java] HttpConnector[8080] Starting background thread
> > >
> >
> > --
> >
=====================================================================
> > Jeffrey D. Brekke
[EMAIL PROTECTED]
> > Wisconsin,  USA
[EMAIL PROTECTED]
> >
[EMAIL PROTECTED]
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to