Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Antonio Petrelli
2007/10/5, Don Brown [EMAIL PROTECTED]: I'm gonna take it to the next level and suggest that our tags should be their own plugin. I am +1 for it. At Tiles we decided to put JSP code in a submodule and everything works pretty well. Antonio

Re: xwork groupId change

2007-10-05 Thread Nils-Helge Garli Hegvik
Are there still no snapshot repository where xwork-2.1-SNAPSHOT is available with the updated groupId? I know I can fix it by building it myself, but I was hoping I could find it somewhere... Nils-H On 9/11/07, Nils-Helge Garli [EMAIL PROTECTED] wrote: I keep getting build failures saying maven

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Ted Husted
On 10/5/07, Don Brown [EMAIL PROTECTED] wrote: 1. Much, much less code in core to maintain 2. Encourage multiple tag libraries (I, for one, would love to see a simple, high performance (read non-Freemarker/limited EL) library) 3. Force us to improve our tag pluggability for plugin authors +1

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Ted Husted
On 10/5/07, Matt Raible [EMAIL PROTECTED] wrote: I would be hesitant about doing this - mostly because no one else does it. If we let that stop us, then there would be no Struts project. :) It might work well for developers, but does it really enhance the users' experience? Speaking as a

WW-1399 - converting mailreader to hsqldb

2007-10-05 Thread Wes Wannemacher
I am poking around for things I can help with. I came across WW-1399 and I remember some discussion before on struts-[dev|user] that hibernate's license is not compatible with apache's. So, assuming we want to use ORM, is there a particular mapper I should look at? I could give this a try with

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Musachy Barroso
2. Encourage multiple tag libraries (I, for one, would love to see a simple, high performance (read non-Freemarker/limited EL) library) That in itself is a good reason for doing it. For people like me, who use the simple theme and never overwrite the ftl files (not so far anyway) would be

Re: SmartURLs MailReader Example (was Re: Should I announce SmartURLs or wait?)

2007-10-05 Thread Ted Husted
On 10/2/07, Brian Pontarelli [EMAIL PROTECTED] wrote: Finally got a chance to look this over. Here's a few things: Thanks, Brian. I'm heads-down on something else right now, but I hope to roll back to the conventions/annotations stuff soon. -Ted.

Re: WW-1399 - converting mailreader to hsqldb

2007-10-05 Thread Wes Wannemacher
I had noticed openjpa when it was in incubation, but I didn't realize it was out and had a 1.0.0 release. If anyone on this list is also a dev on openjpa congrats! -W On 10/5/07, Tom Schneider [EMAIL PROTECTED] wrote: http://openjpa.apache.org/ is an option too. Seems logical since it is an

Re: WW-1399 - converting mailreader to hsqldb

2007-10-05 Thread Tom Schneider
http://openjpa.apache.org/ is an option too. Seems logical since it is an apache project. On 10/5/07, Ted Husted [EMAIL PROTECTED] wrote: On 10/5/07, Wes Wannemacher [EMAIL PROTECTED] wrote: I am poking around for things I can help with. I came across WW-1399 and I remember some discussion

Re: WW-1399 - converting mailreader to hsqldb

2007-10-05 Thread Ted Husted
On 10/5/07, Wes Wannemacher [EMAIL PROTECTED] wrote: I am poking around for things I can help with. I came across WW-1399 and I remember some discussion before on struts-[dev|user] that hibernate's license is not compatible with apache's. So, assuming we want to use ORM, is there a particular

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Matt Raible
On 10/5/07, Ted Husted [EMAIL PROTECTED] wrote: On 10/5/07, Matt Raible [EMAIL PROTECTED] wrote: I would be hesitant about doing this - mostly because no one else does it. If we let that stop us, then there would be no Struts project. :) It might work well for developers, but does it

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Patrick Lightbody
Oh, but one question: I assume if one were to make JSP 2.0-style tags (.tag files) they couldn't be bundled as a plugin, right? - Posted via Jive Forums

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Patrick Lightbody
+1 for sure! - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=135292messageID=207483#207483 - To unsubscribe, e-mail: [EMAIL

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Ian Roughley
I don't think anyone has suggested getting rid of Themes or Freemarker, just making them optional for the folks that don't need/want them. Right now, there's no way to use struts without Freemarker, without writing your own tag library. Well - actually no. You can re-write all the theme

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Ian Roughley
Ah - ok. I think I was reading the s on tags and plug-ins :) So there would be possible 3 different tag libraries: (1) Non-Freemarker/OGNL JSP (2) Exisiting JSP/Freemarker/Velocity (3) Dojo/Ajax plug-in Each of which may or may not be in the same deployment JAR. /ian Ted Husted wrote: I

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Chris Pratt
On 10/5/07, Ian Roughley [EMAIL PROTECTED] wrote: Right now, there's no way to use struts without Freemarker, without writing your own tag library. Well - actually no. You can re-write all the theme files as JSPs and then change the extension in the struts.properties / struts.xml file.

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Ted Husted
On 10/5/07, Chris Pratt [EMAIL PROTECTED] wrote: I don't think anyone has suggested getting rid of Themes or Freemarker, just making them optional for the folks that don't need/want them. Right now, there's no way to use struts without Freemarker, without writing your own tag library. We're

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Brian Pontarelli
I've brought this up before and in a few bug reports but I think that fundamentally fixing the issues that exist with FreeMarker, the tags and OGNL is more important than ripping them out and allowing pluggability. Also, in my not humble opinion, heading back to JSPs seems like just a step

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Martin Cooper
On 10/5/07, Brian Pontarelli [EMAIL PROTECTED] wrote: I've brought this up before and in a few bug reports but I think that fundamentally fixing the issues that exist with FreeMarker, the tags and OGNL is more important than ripping them out and allowing pluggability. Also, in my not humble

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Brian Pontarelli
Martin Cooper wrote: On 10/5/07, Brian Pontarelli [EMAIL PROTECTED] wrote: I've brought this up before and in a few bug reports but I think that fundamentally fixing the issues that exist with FreeMarker, the tags and OGNL is more important than ripping them out and allowing pluggability.

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Ted Husted
On 10/5/07, Brian Pontarelli [EMAIL PROTECTED] wrote: I guess my only fear is that S2 will become much more difficult to get into when new users now have to understand multiple plugins just to get an app up and running. The uber struts.jar solution helps to some degree, but is just hiding the

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Chris Pratt
On 10/5/07, Brian Pontarelli [EMAIL PROTECTED] wrote: This clutter is inside the JAR file and loaded on demand when the tags are used. The size of the JAR file could be reduced by pulling these into a separate JAR, but this still doesn't require a plugin. The idea of the plugin is that

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Brian Pontarelli
Ted Husted wrote: On 10/5/07, Brian Pontarelli [EMAIL PROTECTED] wrote: I guess my only fear is that S2 will become much more difficult to get into when new users now have to understand multiple plugins just to get an app up and running. The uber struts.jar solution helps to some degree, but

Re: [s2] Should tags be their own plugin?

2007-10-05 Thread Ted Husted
On 10/5/07, Brian Pontarelli [EMAIL PROTECTED] wrote: The idea of the plugin is that something is added rather than removed. On 10/5/07, Brian Pontarelli [EMAIL PROTECTED] wrote: I definitely agree on a personal level. But trying to place a framework into a development organization means that