Well, I've heard what JSPX is and learned how to work with it, so guess I'll go back to using JSP. I'd incorrectly assumed everbody was going that way.
With JSPX, besides the different taglib import syntax, and having to use 'CDATA' for HTML codes, I noticed all single elements have to have a backslash at the end, which I guess is an XHTML requirement (ie. <img src="pic.jpg"/>). Also the HTML nesting has to be perfect, or you get a blank paragraph. With JSP, if you nest an HTML tag wrong, you still get an output, but it'll be goofed up until you correct the HTML. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 04, 2005 10:36 PM To: [email protected] Subject: Re: [magnolia-user] error following tutorial If it's just for the purpose of learning, why not. XML is in many concepts (even Jackrabbit Import/Export) very important and eases a lot of interfacing challenges. But using XHTML/JSPX to develop HTML based results is a little exaggerated. Check the output the browser receives, it's HTML. So you really don't need the hassle of dealing with XHTML/JSPX. Magnolia is an excellent playground to explore Java and especially the JSR 170 compliant Content Repository API. Magnolia offers you the great flexibility of creating all sorts of JSPs/Servlets and view the results with the browser. If you follow the basic rule of putting as much functionality as possible into Java Classes or Servlets and use HTML/CSS/JSP for outputting results, you will have reusable and maintainable code. So instead of tranlating to XHTML/JSPX dig deeper into Servlet concepts and OO Design. With the help of so called "Design Patterns" you will learn how to create reusable and easy-to-maintain applications and all of that platform independent (well, that's after all the idea behind Java :-) ). /giancarlo Robert Van Overmeiren wrote: >Yes, I noticed that JSP/HTML would work, but thought I should adapt to >JSPX/XHTML so I can keep up (catch up) with where things are going. An >old PHP scripter, I got into Java to learn about OOP, and whatever else >I can. > >I'm already in the middle of converting my JSP's to JSPX, so may as >well stick with it. > > >-----Original Message----- >From: [email protected] [mailto:[EMAIL PROTECTED] >Sent: Tuesday, October 04, 2005 11:05 AM >To: [email protected] >Subject: Re: [magnolia-user] error following tutorial > >Hi Robert > >Just wanting to add my 2cts on this discussion :-) > >The samples simply give you an idea how to develop templates with XHTML >and JSPX. They are NOT trying to move you towards JSPX and XHTML. These >samples "expect" you to be an HTML crack and therefore want to show you >other additional and interesting possibilities. > >Of course good ol' JSP/HTML is still absolutely oportune. In fact, if >there is no good reason for you to use XHTML based templates, I would >stick to JSP/Java and HTML. 90% of my CMS projects are JSP/HTML/Servlet >based. > >I don't want to launch a discussion about philosphies (JSPX/XHTML vs. >JSP/HTML)! Just added my 2cts :-) > >/giancarlo > > > ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
