Colin,
I was able to get it started, but our idea of debugging is being able to trace a
request from a browser. Is that possible by starting just turbine?

Gabriel

Colin Chalmers wrote:

> Try this code which I sent to my colleagues this morning to help them start
> Turbine within an IDE.
>
> /colin
>
> public class FlsTest
> {
>
>     /** Set of properties that can be used by tasks */
>     private Properties definedProps = new Properties();
>
>  public FlsTest()
>  {
>   TurbineConfig config = null;
>
>   // Setup some defaults from the properties file.
>         try
>         {
>
>    config = new
> TurbineConfig(".","./WEB-INF/conf/TurbineResources.properties");
>    Turbine turbine = new Turbine();
>       turbine.init(config);
>
>         }
>         catch ( Exception e )
>         {
>              e.printStackTrace();
>         }
>
>  }
>
>  public void checkScheduler()
>  {
>   JobEntry jEnt = null;
>
>   try
>
>    ScheduleService ss =
> (ScheduleService)TurbineServices.getInstance().getService(ScheduleService.SE
> RVICE_NAME);
>
> //   jEnt = new JobEntry(1, 1, -1, -1, -1, "PopToQueJob");
>
>   // ss.addJob(jEnt);
>
>   // jEnt = ss.getJob(20);
>  //  System.out.println("first " + jEnt.getTask());
>
>    Vector jobs = ss.listJobs();
>
>    for (int cnt=0; cnt < jobs.size(); cnt++)
>    {
>     jEnt = (JobEntry)jobs.elementAt(cnt);
>
>     System.out.println(jEnt.getTask());
>     System.out.println(jEnt.getPrimaryKeyAsInt());
>    }
>
>     jEnt = ss.getJob(3);
>  //  jEnt.setActive(true);
>
>    WorkerThread lworker = new WorkerThread(jEnt);
>    lworker.run();
> //   jEnt.setActive(false);
> //   lworker.run();
>
>     ScheduledJobLoader sJB = ScheduledJobLoader.getInstance();
>     //    ScheduledJobLoader.getInstance().exec(jEnt,jEnt.getTask());
>     sJB.exec(jEnt, "ServerComJob");
>
>   }
>   catch (Exception e)
>   {
>    System.out.println(e.toString());
>   }
>
>  }
>
>  public void checkSecurity()
>  {
>
>   try
>   {
>        TurbineUser user = (TurbineUser)TurbineSecurity.getUser("Turbine");
>
>    PermissionSet pSet = TurbineSecurity.getAllPermissions();
>
> //   Permission[] perm = pSet.getPermissionsArray();
>
> //   System.out.println(perm[1].getName());
>
>   }
>   catch(Exception e)
>   {
>    System.out.println(e.toString());
>   }
>
>  }
>
>  static public void main(String[] argument) {
>
>  FlsTest fls = new FlsTest();
>
>  try
>  {
>
> // fls.checkScheduler();
>
>  }
>  catch (Exception e)
>  {
>   System.out.println(e.toString());
>  }
>
>  }
> }
>
> ----- Original Message -----
> From: "Gabriel Moreno" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, May 24, 2001 3:59 PM
> Subject: debugging turbine apps
>
> > Hi,
> > We're evaluating turbine to decide whether we use it for a new project
> > or not. We like all the features Turbine provides, but one of the
> > concerns of the team is the ability to debug turbine applications within
> > an IDE. Does anybody have experience with this? I've debugged a little
> > toy by including catalina in the project and starting catalina within
> > the IDE, but it takes 5 minutes just to start catalina.
> >
> > Thanks,
> >
> > Gabriel
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]




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

Reply via email to