You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net> on 2002/06/30 16:34:32 UTC
For Dummies Guide
All,
I'm struggling with developing my first application with turbine. I
understand the torque portions, I think ;).
I need some form of for-dummies guide to building a new application /
application structure. Could someone PLEEEEASSSEEE help....
Cameron
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: For Dummies Guide: IDEs
Posted by Scott Eade <se...@backstagetech.com.au>.
I switched from JBuilder to IntelliJ IDEA some time ago and have never
looked back. JBuilder was for some reason running like a dog on my system
and I was not at all happy with Borland's upgrade policy - i.e. 80% of base
cost for each upgrade.
IntelliJ runs much better and I find it to be much more productive than
JBuilder. Many of the things that required opentools to get working in JB
are just there in IDEA (conversely the opentools API for IDEA is only now
being added).
I tend to use logging to debug rather than the debugger, but I did an
experiment a couple of weeks ago where I connected IDEA to an already
executing catalina instance using remote debugging and it seemed to work. I
guess I could configure IDEA to execute bootstrap as the user that posted
the JB response suggested, but connecting to the already executing catalina
instance seems like a better way to go.
The jakarta velocity site has a set of live templates that assist with
coding velocity pages. Ant and cvs integration are built into IDEA.
If you like living on the edge you can use one of the early access builds of
IDEA (http://www.intellij.com/eap/) to gain access to the current
development builds of the next release of IDEA. This includes numerous
enhancements that I find very useful. The next build (630) will require JDK
1.4 to execute - the main benefit being quicker debugging (the next release
will still support JDK 1.3, but they are focusing on 1.4 for now).
A license for IDEA includes free upgrades for the following 8 months (my
guess is that this is targeting a 6 month release cycle), after this expires
you have access to purchasing new packages at about 50% of the new user
price.
Cheers,
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
> From: Paul Leddy <pc...@yahoo.com>
> Reply-To: "Turbine Users List" <tu...@jakarta.apache.org>
> Date: Sun, 30 Jun 2002 15:31:23 -0700
> To: Turbine Users List <tu...@jakarta.apache.org>
> Subject: For Dummies Guide: IDEs
>
> Curious what IDEs people are using with Turbine/Catalina, their experiments,
> data, nonbiased interpretations:
> - Netbeans
> - JBuilder
> - JDeveloper
> - Hardcore non-IDE
> - Etc.
> - Ant (and integration with above)
>
> Basically, I want very good debugging support, as I have had in the past with
> a
> website built with JBuilder/Tomcat/custom pseudo-EJB infrastructure.
>
> Btw, I searched the archives and only see some simple references to
> Turbine/JBuilder/Tomcat integration -- not Catalina, avoidance -- and some
> rather rude remarks by some very smart people. >snicker<
>
>
>
> =====
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> 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>
For Dummies Guide: IDEs
Posted by Paul Leddy <pc...@yahoo.com>.
Curious what IDEs people are using with Turbine/Catalina, their experiments,
data, nonbiased interpretations:
- Netbeans
- JBuilder
- JDeveloper
- Hardcore non-IDE
- Etc.
- Ant (and integration with above)
Basically, I want very good debugging support, as I have had in the past with a
website built with JBuilder/Tomcat/custom pseudo-EJB infrastructure.
Btw, I searched the archives and only see some simple references to
Turbine/JBuilder/Tomcat integration -- not Catalina, avoidance -- and some
rather rude remarks by some very smart people. >snicker<
=====
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: For Dummies Guide
Posted by Paul Leddy <pc...@yahoo.com>.
if someone sends me a text-based sequence diagram of standard behavior that
turbine exhibits during a typical http request, like login, i'll do up the
sequence diagram in UML, snap an image, post it here, etc. I'd rather see the
actual object names, and not the abstracted ones.
--- Alex McLintock <al...@OWAL.co.uk> wrote:
> At 17:44 30/06/02, someone wrote:
> >I guess the underlying problem is I don't understand the relationship
> >between actions, templates, screens and "page views" correctly.
>
>
> See http://jakarta.apache.org/turbine/turbine-2/fsd.html for more info
>
> or here is my idiots guide.....
>
> When you fetch a web page in a browser you are making a request. What you
> get back is a page.
>
> When an http request is made the thing that you want to happen is the
> action. This is what gets *done*. An action might typically do some change
> to the database, send some email, or whatever. Not all requests have an
> action though....You might just be displaying info in which case no action
> is required. I've been doing web apps for nearly seven years and the action
> here is the same as the action we used on those CGI scripts all that time
> ago even before Java 1.0 was released.
>
> Typically a page that is requested is made up from a number of smaller
> sections such as a header, footer, and menu on the left. The whole thing
> is a page (what you see in the browser). What goes where is controlled by a
> "Layout". I have never changed the layout so know little about them. The
> layout will usually manipulate some navigation sections and the "screen".
> The screen is the important stuff on the page and is often different with
> each page. In contrast the header, footer, and menu are often the same no
> matter which page is displayed. (
>
> We can look at a simple turbine app of mine (and my colleagues) as an example
> http://www.owal.co.uk/oss_support/
> It is not a lot more than the newapp which comes with the Turbine
> Development Kit tdk.
> It is a simple database of companies that use, support, and develop Open
> Source Software.
> (So if you want to shout out to the world that you are a Struts expert then
> submit your details :-)
>
> There is a simple header with a pretty image and slogan. (This is defined
> in DefaultTop.vm )
> There is a simple footer with several pretty images and slogans. (This is
> defined in DefaultBottom.vm )
> There is a simple menu on the left defined in Menu.vm.
>
> The rest of the page is a "screen".
>
> So how do we say what goes in a screen?
>
> Basically you say what template you want, and you usually do that by
> specifying it in the link.
> Of course there is a default template (typically INdex.vm) but the
> principle is the same.
>
> Select "search for a company" and you get a new page, with the same
> navigation tools, but a new screen.
> The link is
> http://www.owal.co.uk/oss_support/servlet/newapp/template/CompanySearch.vm
> which hopefully suggests to you that the template is "CompanySearch.vm"
> CompanySearch.vm is a velocity file which like ASP or JSP is souped up html
> BUT it doesn't actually
> figure out what goes there. There is no way to insert Java into a velocity
> page.
>
> So how does the screen and the template get this information (the list of
> open source packages).
> Well the "system" sees that CompanySearch.vm is needed here and
> automatically searches for
> a java class called CompanySearch to "help" it. My class COmpanySearch goes
> to the database,
> sees what it is supposed to offer the user, and inserts the necessary data
> into a thing called a context.
> The context is basically the environment of the velocity template - it can
> "see" the context, and nothing else.
>
> Click on one of the OSS packages listed such as "Apache Turbine" and you
> will reach this page
>
>
http://www.owal.co.uk/oss_support/servlet/newapp/template/CompanySearchResults.vm/pid/4
>
> Here we have a new template, which results in a new page, but of course the
> navigation elements are the same.
>
> CompanySearchResults displays the results of a search for a company (well
> duh!). It gets its info from a
> java class "CompanySearchResults" which does the actual search. But what
> does it search on?
> well it needs to have some parameter and in this case it is the package
> identifier (or "pid") which has the value 4.
>
> The template doesn't care - it just knows that it is supposed to display a
> list of companies which some other code
> will provide it through its context.
>
>
>
>
> And that is all I am typing on the subject today. If people ask for it I can
>
> a) write more in the same way (but perhaps clearer)
> b) discuss how to add new features to this app - eg a search by company
> location
> c) Turn this application into a well documented super-newapp which could be
> used as an example of how to do things in Turbine.
>
>
>
> Alex McLintock
>
>
>
>
>
>
> Openweb Analysts Ltd, London: Software For Complex Websites
> http://www.OWAL.co.uk/
> Free Consultancy for London Companies thinking of Open Source Software.
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
=====
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: For Dummies Guide
Posted by Alex McLintock <al...@OWAL.co.uk>.
At 17:44 30/06/02, someone wrote:
>I guess the underlying problem is I don't understand the relationship
>between actions, templates, screens and "page views" correctly.
See http://jakarta.apache.org/turbine/turbine-2/fsd.html for more info
or here is my idiots guide.....
When you fetch a web page in a browser you are making a request. What you
get back is a page.
When an http request is made the thing that you want to happen is the
action. This is what gets *done*. An action might typically do some change
to the database, send some email, or whatever. Not all requests have an
action though....You might just be displaying info in which case no action
is required. I've been doing web apps for nearly seven years and the action
here is the same as the action we used on those CGI scripts all that time
ago even before Java 1.0 was released.
Typically a page that is requested is made up from a number of smaller
sections such as a header, footer, and menu on the left. The whole thing
is a page (what you see in the browser). What goes where is controlled by a
"Layout". I have never changed the layout so know little about them. The
layout will usually manipulate some navigation sections and the "screen".
The screen is the important stuff on the page and is often different with
each page. In contrast the header, footer, and menu are often the same no
matter which page is displayed. (
We can look at a simple turbine app of mine (and my colleagues) as an example
http://www.owal.co.uk/oss_support/
It is not a lot more than the newapp which comes with the Turbine
Development Kit tdk.
It is a simple database of companies that use, support, and develop Open
Source Software.
(So if you want to shout out to the world that you are a Struts expert then
submit your details :-)
There is a simple header with a pretty image and slogan. (This is defined
in DefaultTop.vm )
There is a simple footer with several pretty images and slogans. (This is
defined in DefaultBottom.vm )
There is a simple menu on the left defined in Menu.vm.
The rest of the page is a "screen".
So how do we say what goes in a screen?
Basically you say what template you want, and you usually do that by
specifying it in the link.
Of course there is a default template (typically INdex.vm) but the
principle is the same.
Select "search for a company" and you get a new page, with the same
navigation tools, but a new screen.
The link is
http://www.owal.co.uk/oss_support/servlet/newapp/template/CompanySearch.vm
which hopefully suggests to you that the template is "CompanySearch.vm"
CompanySearch.vm is a velocity file which like ASP or JSP is souped up html
BUT it doesn't actually
figure out what goes there. There is no way to insert Java into a velocity
page.
So how does the screen and the template get this information (the list of
open source packages).
Well the "system" sees that CompanySearch.vm is needed here and
automatically searches for
a java class called CompanySearch to "help" it. My class COmpanySearch goes
to the database,
sees what it is supposed to offer the user, and inserts the necessary data
into a thing called a context.
The context is basically the environment of the velocity template - it can
"see" the context, and nothing else.
Click on one of the OSS packages listed such as "Apache Turbine" and you
will reach this page
http://www.owal.co.uk/oss_support/servlet/newapp/template/CompanySearchResults.vm/pid/4
Here we have a new template, which results in a new page, but of course the
navigation elements are the same.
CompanySearchResults displays the results of a search for a company (well
duh!). It gets its info from a
java class "CompanySearchResults" which does the actual search. But what
does it search on?
well it needs to have some parameter and in this case it is the package
identifier (or "pid") which has the value 4.
The template doesn't care - it just knows that it is supposed to display a
list of companies which some other code
will provide it through its context.
And that is all I am typing on the subject today. If people ask for it I can
a) write more in the same way (but perhaps clearer)
b) discuss how to add new features to this app - eg a search by company
location
c) Turn this application into a well documented super-newapp which could be
used as an example of how to do things in Turbine.
Alex McLintock
Openweb Analysts Ltd, London: Software For Complex Websites
http://www.OWAL.co.uk/
Free Consultancy for London Companies thinking of Open Source Software.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: For Dummies Guide
Posted by "Anthony W. Marino" <an...@AWMObjects.com>.
Is there going to be much of a fundamental difference between 2x and 3x
versions of Turbine that one should concern themselves with? Should one just
getting started with Turbine thus use T3 instead of T2?
Thank You,
Anthony
> Not to sound harsh, but have you looked at this:
> http://jakarta.apache.org/turbine/turbine-2/fsd.html
>
> I think it explains them pretty well, but I'll break it down simply.
> Page - it contains and coordinates the templates, screens and actions, so
> you don't need to worry about it, just understand it
> Screen - your content
> Layouts - how your page will look, plus your content
> Navigation - common navigation for your webapp
> Action - what you want to happen before a page gets called
>
> All of these rely on a common naming scheme (ie - if there is a screen with
> the name admin, then Turbine will look for corresponding Admin.java for
> actions or Admin.vm for layouts)
>
> In addition you can go with a Pull Model instead of Actions:
> http://jakarta.apache.org/turbine/turbine-2/pullmodel.html
> http://jakarta.apache.org/turbine/turbine-2/howto/pullmodel-howto.html
>
> This goes into greater detail on setting up Velocity:
> http://jakarta.apache.org/turbine/turbine-2/howto/velocity-site-howto.html
> http://jakarta.apache.org/turbine/turbine-2/howto/context-howto.html
>
> Believe me, once you get into it, it'll be hard using other systems =).
> I've done Struts/JSP programming and I much rather enjoy Turbine/Velocity
> programming. There are some features that I like about Struts, and I hope I
> will be able to help bringing in some of those as I get time ;-).
>
> I hope this helps.
>
> -warner
>
> ----- Original Message -----
> From: "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>
> To: "'Turbine Users List'" <tu...@jakarta.apache.org>
> Sent: Sunday, June 30, 2002 9:44 AM
> Subject: RE: For Dummies Guide
>
> > Sorry to add to the volume,
> >
> > I guess the underlying problem is I don't understand the relationship
> > between actions, templates, screens and "page views" correctly.
> >
> > I have a good grasp of the Struts ideology, but not turbine.
> >
> > Any pointers?
> >
> > -----Original Message-----
> > From: Warner Onstine [mailto:sw-list@warneronstine.com]
> > Sent: 30 June 2002 17:24
> > To: Turbine Users List
> > Subject: Re: For Dummies Guide
> >
> >
> > Have you checked out the TDK and the sample app, it is very explanatory.
> >
> > -warner
> >
> > ----- Original Message -----
> > From: "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>
> > To: <tu...@jakarta.apache.org>
> > Sent: Sunday, June 30, 2002 7:34 AM
> > Subject: For Dummies Guide
> >
> > > All,
> > >
> > > I'm struggling with developing my first application with turbine. I
> > > understand the torque portions, I think ;).
> > >
> > > I need some form of for-dummies guide to building a new application /
> > > application structure. Could someone PLEEEEASSSEEE help....
> > >
> > >
> > > Cameron
> > >
> > >
> > > --
> > > 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>
> >
> >
> >
> >
> > --
> > 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: For Dummies Guide
Posted by Warner Onstine <sw...@warneronstine.com>.
Not to sound harsh, but have you looked at this:
http://jakarta.apache.org/turbine/turbine-2/fsd.html
I think it explains them pretty well, but I'll break it down simply.
Page - it contains and coordinates the templates, screens and actions, so
you don't need to worry about it, just understand it
Screen - your content
Layouts - how your page will look, plus your content
Navigation - common navigation for your webapp
Action - what you want to happen before a page gets called
All of these rely on a common naming scheme (ie - if there is a screen with
the name admin, then Turbine will look for corresponding Admin.java for
actions or Admin.vm for layouts)
In addition you can go with a Pull Model instead of Actions:
http://jakarta.apache.org/turbine/turbine-2/pullmodel.html
http://jakarta.apache.org/turbine/turbine-2/howto/pullmodel-howto.html
This goes into greater detail on setting up Velocity:
http://jakarta.apache.org/turbine/turbine-2/howto/velocity-site-howto.html
http://jakarta.apache.org/turbine/turbine-2/howto/context-howto.html
Believe me, once you get into it, it'll be hard using other systems =). I've
done Struts/JSP programming and I much rather enjoy Turbine/Velocity
programming. There are some features that I like about Struts, and I hope I
will be able to help bringing in some of those as I get time ;-).
I hope this helps.
-warner
----- Original Message -----
From: "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>
To: "'Turbine Users List'" <tu...@jakarta.apache.org>
Sent: Sunday, June 30, 2002 9:44 AM
Subject: RE: For Dummies Guide
> Sorry to add to the volume,
>
> I guess the underlying problem is I don't understand the relationship
> between actions, templates, screens and "page views" correctly.
>
> I have a good grasp of the Struts ideology, but not turbine.
>
> Any pointers?
>
> -----Original Message-----
> From: Warner Onstine [mailto:sw-list@warneronstine.com]
> Sent: 30 June 2002 17:24
> To: Turbine Users List
> Subject: Re: For Dummies Guide
>
>
> Have you checked out the TDK and the sample app, it is very explanatory.
>
> -warner
>
> ----- Original Message -----
> From: "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>
> To: <tu...@jakarta.apache.org>
> Sent: Sunday, June 30, 2002 7:34 AM
> Subject: For Dummies Guide
>
>
> > All,
> >
> > I'm struggling with developing my first application with turbine. I
> > understand the torque portions, I think ;).
> >
> > I need some form of for-dummies guide to building a new application /
> > application structure. Could someone PLEEEEASSSEEE help....
> >
> >
> > Cameron
> >
> >
> > --
> > 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>
>
>
>
>
> --
> 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: For Dummies Guide
Posted by "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>.
Sorry to add to the volume,
I guess the underlying problem is I don't understand the relationship
between actions, templates, screens and "page views" correctly.
I have a good grasp of the Struts ideology, but not turbine.
Any pointers?
-----Original Message-----
From: Warner Onstine [mailto:sw-list@warneronstine.com]
Sent: 30 June 2002 17:24
To: Turbine Users List
Subject: Re: For Dummies Guide
Have you checked out the TDK and the sample app, it is very explanatory.
-warner
----- Original Message -----
From: "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>
To: <tu...@jakarta.apache.org>
Sent: Sunday, June 30, 2002 7:34 AM
Subject: For Dummies Guide
> All,
>
> I'm struggling with developing my first application with turbine. I
> understand the torque portions, I think ;).
>
> I need some form of for-dummies guide to building a new application /
> application structure. Could someone PLEEEEASSSEEE help....
>
>
> Cameron
>
>
> --
> 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>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: For Dummies Guide
Posted by "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>.
Yes I did, I can't quite grasp it... Any other useful resources?
-Cameron
-----Original Message-----
From: Warner Onstine [mailto:sw-list@warneronstine.com]
Sent: 30 June 2002 17:24
To: Turbine Users List
Subject: Re: For Dummies Guide
Have you checked out the TDK and the sample app, it is very explanatory.
-warner
----- Original Message -----
From: "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>
To: <tu...@jakarta.apache.org>
Sent: Sunday, June 30, 2002 7:34 AM
Subject: For Dummies Guide
> All,
>
> I'm struggling with developing my first application with turbine. I
> understand the torque portions, I think ;).
>
> I need some form of for-dummies guide to building a new application /
> application structure. Could someone PLEEEEASSSEEE help....
>
>
> Cameron
>
>
> --
> 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>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: For Dummies Guide
Posted by Warner Onstine <sw...@warneronstine.com>.
Have you checked out the TDK and the sample app, it is very explanatory.
-warner
----- Original Message -----
From: "Gray, Cameron C. [UltraSpeed]" <CG...@UltraSpeed.net>
To: <tu...@jakarta.apache.org>
Sent: Sunday, June 30, 2002 7:34 AM
Subject: For Dummies Guide
> All,
>
> I'm struggling with developing my first application with turbine. I
> understand the torque portions, I think ;).
>
> I need some form of for-dummies guide to building a new application /
> application structure. Could someone PLEEEEASSSEEE help....
>
>
> Cameron
>
>
> --
> 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>