Hi Mike. I have been playing with that concept. Nice and simple, yes. Appropriate? I have been trying to figure that out.
It would mean changing a core API a little bit, which seems to ruffle feathers sometimes. Sneak it in now? I can make the change to both Persistent services at this point. But this is not my call. I have the code ready to go (it was a fairly simple enhancement) if that is the decision. Otherwise, I will hold onto it until it is decided to start checking in new enhancements. I can also readily drop it if somebody comes up with a better or more appropriate idea. Regards, Steve -- Java/J2EE Developer/Integrator Currently "On the Road" 214-724-7741 Platform Independance Rules. Give me a stable platform, and I will give you stable code. ----- Original Message ----- From: Michael Nash JGlobal.com Sent: 10/2/2003 6:25:08 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Keelgroup] Struts Headache, help? > Steve: > > > Not quite. I am putting things together in two separate operations, the titles in > > one, and the results of the query in another (using addQuery). The results are > > being displayed in a different order from the titles. > > So they might well be being added in different orders by the Model itself, I see > what you mean. > > > Bottom line, they are not getting put together in a consistent order in the Model. > > So the JSP has absolutely no chance to deal with it. > > Here's a thought: If addQuery took an (option) list of field names, it could > populate the outputs it builds in that order - then it should line up with the > headers, not to mention adding additional capability to addQuery. It's an API > change, though, but maybe a worthwhile one. OTOH, we could just clone addQuery and > add that capability within the specific model, but that's more of a quick fix :-) > > > One approach I am looking at is since the "columns" are put into the "rows" by > > Column (or Field) name, and the JSP has access to this from the Titles (which are > > also put in the Output by Field Name) was to have the JSP pull > > stuff out by field name. This would also allow for the user to be able to select > > the order the columns were displayed in later, especially when implementing via a > > GUI client. > > Means more work in the GUI side, but that would work too. > > Strictly off on a tangent, but these are exactly the kind of issues that JSF > (JavaServer Faces) will deal with in a better way. I'm sure once that standard holds > still for a while we'll be looking at ways to incorporate it, and make this kind of > thing not only easier, but highly standardized. I understand Sun will even be making > a GUI "builder" for JSF front-ends, which will be handy in some situations. > > Regards, > > Michael Nash > > JGlobal Ltd. > http://www.jglobal.com > > Bahamas Commerce and Trade > http://www.bahamascommerce.com > > http://keelframework.org/documentation > Keelgroup mailing list > [EMAIL PROTECTED] > http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
