As I said before, nothing has been set in stone yet. I know David has evaluated Struts+Tiles and felt it was more then he wanted to attempt at the time.
As work progresses, we will get a better idea of what will best serve Jetspeed 2 development. I am all for using Struts and have even proposed its integration into Js1. When the time comes to choose a supporting framework I am sure a fair evaluation as is possible will be made between the two frameworks. *===================================* * Scott T Weaver������������������� * * Jakarta Jetspeed Portal Project�� * * [EMAIL PROTECTED] * *===================================* � > -----Original Message----- > From: Mete Kural [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 28, 2003 6:20 AM > To: Jetspeed Users List > Subject: RE: JetSpeed 2: Turbine or Struts? > > > Thanks for your input. The reason why I was wondering about this topic is > because Struts has industry-wide tools support and it seems like this > support is going to increase in the future. Additionally Struts has/will > have good integration with JavaServer Faces which I think is crucial for a > portal server such as JetSpeed in order to be truly client agnostic. > Furthermore there are a lot of developers familiar with Struts which may > get more developers interested in committing to JetSpeed. What do you > think? Do you think these factors are worth the hassle of switching from > Turbine to Struts as the base framework layer? > > Mete > > ---------- Original Message ---------------------------------- > From: "Weaver, Scott" <[EMAIL PROTECTED]> > Reply-To: "Jetspeed Users List" <[EMAIL PROTECTED]> > Date: Wed, 28 May 2003 13:27:25 -0400 > > >So far, there is no framework behind Js2, though Fulcrum is currently > being used to build services. I have a feeling that the framework will > more than likely be Turbine as that is what most of the Js2 developers > have the most experience with, however I cannot verify anything. > Personally, I have created stand alone apps with both frameworks and I > think either one would work well as a supporting framework for the > container. > > > >The good news is that the structure of portlet applications are defined > in a similar manner to the way web applications are, so using Struts to > support your portlets/portlet applications should be relatively straight > forward. > > > >I know it's not much but, that's about all I can say for now ;) > > > > > >hth, > >*===================================* > >* Scott T Weaver������������������� * > >* Jakarta Jetspeed Portal Project�� * > >* [EMAIL PROTECTED] * > >*===================================* > > > > > > > >> -----Original Message----- > >> From: Mete Kural [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, May 28, 2003 3:37 AM > >> To: Jetspeed Users List > >> Subject: JetSpeed 2: Turbine or Struts? > >> > >> >Jetspeed-2 is being developed as we speak. Sorry, I have no dates yet. > >> > >> Will JetSpeed 2 use Turbine as its base framework or Struts? If it is > >> still based on Turbine, what kind of major architectural changes are > >> expected and what will be the role of Struts in JetSpeed 2 if any. > >> > >> Thanks, > >> Mete > >> > >> > >> --------------------------------------------------------------------- > >> 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]
