Hi,
> Hi,
>
> I am planning to use Turbine for my upcoming project. I have been using
WebMacro so far >to generate my front end and with WebMacro integration in
Turbine and many more >additional capabilities, I am interested in using it.
Great! Take a look at the TDK (Turbine Developers Kit).
> I would like to skip the user authentication from the database as is done
by Turbine servlet at >present and put up my own authentication. Also I
would not like to use the Turbine to connect >to my database directly as we
have our middleware to do the same.
Just don't call the Turbine User or the Turbine Database stuff and you'll
never know it's there. If you don't even want Turbine to use a default user
you can write your own SessionValidator. This should be easy - just don't
do anything about session validation :-)
> I would like to use Turbine only to handle the requests coming in from the
browser and serve >up the pages(combinations of may screens in a single
page) based on what is been requested. >The data would be handed over to it
by the seperate API which responsible for getting the >same from the
middleware.
As long as your middleware is Java you'll probably have smooth sailing. As
far as multiple screens per page is concerned: I don't really understand
what you mean by that. You might want to take a look at JetSpeed, but I
have a feeling this is not entirely what you have in mind...
> Can anyone comment on this and let me know how to skip the database part
in Turbine >servlet. I do not want to even fire up the connection poolong.
I know that with the >capabilities Turbine has, this may seem to be a little
thing but I would still like to have the >option to connect to Database in
future if necessary.
Then you just call the database methods and it'll fire up the connection
pool as soon as you need it.
> We use Progress database. Can we connect to it using Sequelink database if
required in >future ?
I don't know Sequelink at all. Theoretically Turbine can connect with any
JDBC db. If you have trouble with yours I recommend that you take a look at
db_adapters.html (or this was what is was called last time I checked :-) on
how to create a Turbine adapter class for your favourite db...
> Thanks
>
> Venkat
>
> Venkata Subbarao Pathuri
> Java Developer
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
