Re: Submission... display:table... tag library

2002-01-08 Thread Don Saxton

yes, this will be a significant contribution.  Just the right stuff for a
public taglib, it will be interesting to see how it evolves. I especially
like the writing in the examples and its sensitivity to usage. I hope you
get a chance to carry that over to the documentation you suggest.

bravo.

- Original Message -
From: Ed Hill [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, January 07, 2002 12:37 PM
Subject: Submission... display:table... tag library


 Hello,

 A few weeks ago, I mentioned in the struts-user list a tag library that we
 are developing which at the time I called gui:table...  I didn't have the
 source ready to go at the time - but rather then trying to get it perfect
in
 isolation, I'll risk the public humiliation and go ahead and make
available
 what I have now and try to work with others who are interested in
 helping me polish it up.

 Currently, this taglib has a single key tag called table that takes a
list
 of objects and displays them as a table.  It has various features
 (alternating row colors, using a decorator for formatting, sorting,
 pagination, etc...)

 My goal over time will be to add other common high-level web display
 patterns to the tag library, for example:

- display:table
- display:tree
- display:tabs
- display:inspector
- etc...

 The source to this tag library is available at:

 http://edhill.its.uiowa.edu/downloads/display.zip

 Examples, showing usage can be found at:

 http://edhill.its.uiowa.edu/display-examples/

 Currently, documentation is little more then just the examples.

 To be honest, my original intention was to donate this taglib to struts if
 there was interest, as we are heavy struts users here at the U of Iowa,
and
 I wanted to give back if possible, but there is nothing struts-specific
 about the taglib (other then using some struts-like naming conventions for
 attributes), so it is probably more appropriately a candidate for the
taglib
 project, and as such, I have been working on getting the build process for
 the tag working in a jakarta-taglib style.

 I welcome any and all feedback and advice.  If this taglib seems like
 something that would be useful for either struts or taglibs, please let me
 know, and I'll be happy to work with either group to get it put into CVS
and
 on a more serious release schedule.

 I am currently being presumptuous, and have the taglib living in the
 org.apache.taglibs.display package, but if this doesn't seem like
something
 that would be of use to taglibs, I will certainly change the packaging to
 something more appropriate.

 Thanks.

 -Ed Hill ([EMAIL PROTECTED])
 Software Developer - Information Technology Services - University of Iowa




 --
 To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
mailto:[EMAIL PROTECTED]



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Nested tags

2002-01-08 Thread Ted Husted

Arron Bates wrote:
 
 Excuse the ignorance, but how will the multiple-servlet controller
 change the way JSP views work?...
 I could possibly imagine a change to the form tag, but that would be it
 wouldn't it?... (yes/no Craig?)
 
 There's been a couple of updates (one is related to the Resin bug that
 was just submitted. That was fun) some refactoring of the helper class
 to make it more generally usable for developers wanting to make their
 own nested tags. But it's still working as it should.
 
 ASF can still have it if they want it.
 I've finished the primer and a step-by-step tutorial which I want to cap
 off with a little extension to complete the training on the extension
 (always two there are). ASF want them too?...

Well, yeah :)

 
 I still haven't put a spiel out on the user list yet (Tom's done so a
 few times, and I've seen a post on jGuru :).
 I'll hold off if it's going to be committed.

Don't hold off, the more community you build around it first, the
better. 


-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Building Java web applications with Struts.
-- Tel +1 585 737-3463.
-- Web http://www.husted.com/struts/

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




NestedCheckboxTag

2002-01-08 Thread Tom Klaasen (TeleRelay)

Arron,

I just had the need to have a NestedCheckboxTag. Maybe you should
include it.

cheers,
tomK



nested-checkbox.zip
Description: nested-checkbox.zip

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]


RE: Generic JSP

2002-01-08 Thread Taylor Cowan

You're going about this the hard way.  The solution involves XML and XSLT.
The XML can be produced on the fly, while the XSLT doc is static.

Taylor

-Original Message-
From: Sidhartha Jain [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 08, 2002 8:17 AM
To: Struts Developers List
Subject: Generic JSP



Hi All,
I need to develop a Generic JSP using struts framework.I would explain you
my problem.
We have few links on page that represents the Objects corresponding to which
we already have some classes built.

We also have tables in the database corressponding to each and every class
and columns in the table are same as the variables of the class.
For eg : We have an employee class with employee name, Employee number etc
etc as fields so we have a
table also corresponding to that.

Now whenever anyone clicks on these objects link we need to create a JSP on
fly taking out the variable names(same as column names in database) and
their type .While displaying on the JSP we need to replace them by
appropriate field labels (Might be stored in database or properties file
which will also have priorties of displaying the field ) and also display
text box etc etc according  field type and then also we should have some
priorities like which field would come first and which field would come
second on the page.

This way we create a generic JSP on fly and when you click on any object
link u get a JSP with its respective fields wheer u type the data and press
save and data is committed in the database.

I read in an article that this was a struts limitaion in Version 1.0 that it
could not handle dynamic properties whether by database or properties file.
the link for the article is
http://www.zdnetindia.com/techzone/coding/stories/22419.html

So i just wanted to ask whether is this possible to achieve if yes how and
if someone has done this sort of work and he could bail me out of this
problem that would of great help.
Could anyone help me out with the solution to this problem.If someone needs
some more information specific one about this please mail me I would write
more on it.Hope I have explained it here.


Thanks
Sidh








--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




DO NOT REPLY [Bug 5739] New: - Struts fails silently in too many places

2002-01-08 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5739.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5739

Struts fails silently in too many places

   Summary: Struts fails silently in too many places
   Product: Struts
   Version: 1.0 Final
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Controller
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When something is specified incorrectly, usually in
struts-config.xml or invocation of struts methods,
the result is nothing!  No exception, no log entry.

Among the people I work with and from many forum posts
it seems like this is a common source of frustration 
for struts developers.  Some specific examples:

- If the ActionForm name is not defined in struts-config, silence
- If the ActionForward string is not found, silence
- If no app.properties found, pretty close to silence
- if you say html:text indexed=yes (should be true), silence
  (note, the documentation implies it should be yes)
  (many tag errors just result in silence)
- If the ActionError type is not found, silence

Most of these should cause exceptions and/or log entries.

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




DO NOT REPLY [Bug 5739] - Struts fails silently in too many places

2002-01-08 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5739.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5739

Struts fails silently in too many places





--- Additional Comments From [EMAIL PROTECTED]  2002-01-08 08:05 ---
One thing brought up in the past on the dev list is that Struts doesn't 
complain when there are duplicates in the config file.  For example two form 
beans with the same name, etc.

This should be easy to catch and log.  I can submit a patch if others are 
interested.

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: [VOTE] Release Struts 1.0.1-rc1 as Struts 1.0.1

2002-01-08 Thread Oleg V Alexeev

Hello Martin,

Thursday, January 03, 2002, 9:51:08 AM, you wrote:

 --
 Vote:  Release Struts 1.0.1-rc1 as Struts 1.0.1
 [ ] +1  I am in favor of the release, and will help support it
 [X] +0  I am in favor of the release, but am unable to help support it
 [ ] -0  I am not in favor of the release
 [ ] -1  I am against this proposal (must include a reason).
 --

-- 
Best regards,
 Olegmailto:[EMAIL PROTECTED]



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Building Form Beans from XML Schema?

2002-01-08 Thread Jon Ferguson

( Republished under appropriate Subject :-( ).

Hey,

I've been toying with the idea of Modelling my form beans using XML Schema,
then generating the actual beans using some XML binding tool like Castor (which
should also generate my validate function).  I should also be able to use
Castor to do RDBMS mapping as well.. (but from a session bean manipulating the
formbeans for example).

I'm thinking of utilising schema from developments such as RosettaNet, BizTalk
Frameworks and ebXML - noting that often the info entered into forms could be
the same message information that might be passed between businesses. (Eg. a
Purchase Order, etc.).

I'm hoping that the result would: a) help to standardize the business app. b)
leave it wide open for making use of b-2-b developments such as webServices and
the above efforts. c) provide automatic form validation (inherent in the
Schema), d) obviate the  hand-coading of formbeans.

Any comments on this approach?  Has anyone tried this?

Cheers,

Jon



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]


Re: Generic JSP

2002-01-08 Thread Ted Husted

Can we move this over to the User list?

Taylor Cowan wrote:
 
 You're going about this the hard way.  The solution involves XML and XSLT.
 The XML can be produced on the fly, while the XSLT doc is static.
 
 Taylor
 
 -Original Message-
 From: Sidhartha Jain [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, January 08, 2002 8:17 AM
 To: Struts Developers List
 Subject: Generic JSP
 
 Hi All,
 I need to develop a Generic JSP using struts framework.I would explain you
 my problem.
 We have few links on page that represents the Objects corresponding to which
 we already have some classes built.
 
 We also have tables in the database corressponding to each and every class
 and columns in the table are same as the variables of the class.
 For eg : We have an employee class with employee name, Employee number etc
 etc as fields so we have a
 table also corresponding to that.
 
 Now whenever anyone clicks on these objects link we need to create a JSP on
 fly taking out the variable names(same as column names in database) and
 their type .While displaying on the JSP we need to replace them by
 appropriate field labels (Might be stored in database or properties file
 which will also have priorties of displaying the field ) and also display
 text box etc etc according  field type and then also we should have some
 priorities like which field would come first and which field would come
 second on the page.
 
 This way we create a generic JSP on fly and when you click on any object
 link u get a JSP with its respective fields wheer u type the data and press
 save and data is committed in the database.
 
 I read in an article that this was a struts limitaion in Version 1.0 that it
 could not handle dynamic properties whether by database or properties file.
 the link for the article is
 http://www.zdnetindia.com/techzone/coding/stories/22419.html
 
 So i just wanted to ask whether is this possible to achieve if yes how and
 if someone has done this sort of work and he could bail me out of this
 problem that would of great help.
 Could anyone help me out with the solution to this problem.If someone needs
 some more information specific one about this please mail me I would write
 more on it.Hope I have explained it here.
 
 Thanks
 Sidh

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




accessibility issue (?) in the html tag lib.

2002-01-08 Thread [eb]


i have a question i'm hoping someone can deliver a response to.

first things:  i'm running struts' nightly build from jan 2, tomcat 4.0.1,
and am using windows 2K, though deployment will be on solaris 8.

in our html code, we include in very nearly every tag an 'alt' and 'title'
attribute -- these attributes allow screen-reading software to aid the
visually impaired in understanding out websites.  since we're a government
agency, we're reaquired to do this.

when using the html tag lib, i tried adding these attributes to the tags,
and the title attribute works fine, provided i add it specifically to the
taglib definition of the tag i'm using (makes sense), however alt doesn't.

the issue here is that some screen readers use 'alt' and some use 'title'
in practice.  it'd be helpful if alt were handled in BaseTag as title is.

--ben

B.Vandgrift [EMAIL PROTECTED]http://www.evilbastard.com 


   We are all our own graveyards; we squat amongst the tombs of the
 people we were. -- Clive Barker



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Nested tags

2002-01-08 Thread Craig R. McClanahan



On Tue, 8 Jan 2002, Arron Bates wrote:

 Date: Tue, 08 Jan 2002 10:33:55 +1100
 From: Arron Bates [EMAIL PROTECTED]
 Reply-To: Struts Developers List [EMAIL PROTECTED]
 To: Struts Developers List [EMAIL PROTECTED]
 Subject: Re: Nested tags

 Excuse the ignorance, but how will the multiple-servlet controller
 change the way JSP views work?...

In theory, it shouldn't change anything at all.  You should be able to
take an existing Struts-based app (i.e. a struts-config.xml file and it's
associated resources) and have it run -- then take that app and make it a
subapp in some multi-sub-app environment, with zero changes.

The current approach (which looks the most promising from all the ones
I've tried) is based on the following principles:

* Single ActionServlet instance is still used to manage everything.

* Multiple independent struts-config.xml files (one per sub-app),
  with independent configuration of stuff that is currently set as
  servlet initialization parameters, and an application resources
  bundle per sub-app.

* Sub-applications are distinguished by having a unique prefix to the
  context relative portion of the URI (similar to the way that a
  servlet container distinguishes webapps based on the context path).
  Thus, you might have three subapps with context-relative paths that
  follow these patterns:
/catalog/*  Product catalog
/store/*Shopping cart
/*  Default sub-app that is used
for all requests not matched to
another sub-app

* Servlet mappings to ActionServlet work one of two ways, depending
  which style you like:
  - For extension mapping, continue to use *.do or whatever as before.
  - For path mapping, you'll want to set up more than one sub-app
relative path mapping:
  servlet-mapping
servlet-nameaction/servlet-name
url-pattern/catalog/do/*/url-pattern
  /servlet-mapping
  servlet-mapping
servlet-nameaction/servlet-name
url-pattern/store/do/*/url-pattern
  /servlet-mapping
  servlet-mapping
servlet-nameaction/servlet-name
url-pattern/do/*/url-pattern
  /servlet-mapping

* Paths that are automatically converted to context-relative today (like
  the page attribute on html:link are automatically converted to
  sub-app-relative paths instead.  A special attribute will be added so
  you can create ActionForward definitions that really are context
  relative (i.e. a menu that lets you switch sub-apps).

Doing all this has pretty significant impact on the internals of the
controller, but so far it only needs one very small tweak to the APIs that
a typical Struts application would use.  But, I'm not done yet ...

 I could possibly imagine a change to the form tag, but that would be it
 wouldn't it?... (yes/no Craig?)


I need to look more at this.

 There's been a couple of updates (one is related to the Resin bug that
 was just submitted. That was fun) some refactoring of the helper class
 to make it more generally usable for developers wanting to make their
 own nested tags. But it's still working as it should.


If Resin is not implementing the spec correctly, I'm not interested in
changing Struts to accomodate it.  And don't think I'm picking on just
them - I wouldn't check in the workaround for WebSphere (which didn't
allow deleting request attributes for a while) either.

 ASF can still have it if they want it.
 I've finished the primer and a step-by-step tutorial which I want to cap
 off with a little extension to complete the training on the extension
 (always two there are). ASF want them too?...

 I still haven't put a spiel out on the user list yet (Tom's done so a
 few times, and I've seen a post on jGuru :).
 I'll hold off if it's going to be committed.


Personally, I really want to focus on the controller updates first ...
then, I will look at nested tags.


 Arron.


Craig



 Ted Husted wrote:

 Arron,
 
 Once Craig's implementation of the multi-servlet controller comes out,
 do you think you would have a chance to try and update your nested
 taglib?
 
 http://www.keyboardmonkey.com/struts/index.html
 
 At that point [SHORT TERM PLAN ALERT], I'd like to commit it to the
 nightly build, assuming you would still like to donate it to the ASF.
 
 -Ted.
 
 
 
 Tom Klaasen (TeleRelay) wrote:
 
 For the record:
 
 I've been playing with Arron's nested tags for a while now, and they
 seem OK to me. I've had the occasional what the #$%#@ when something
 didn't work as I expected, but after thinking about it the reason was
 obvious. This situation occurs with most struts tags (for me, in any
 case :P), so they do conform to struts standards ;)
 
 tomK
 


 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Possible bug: Present Struts 1.0 PropertyUtils introspection code bonks on the variety of Tomcat 4 ServletRequest facades that get handed to us as HttpServletRequest

2002-01-08 Thread James Dasher

Whoever thought of bean:page, I love it, but it exposes some weird
introspection inconsistencies in the Tomcat container, and I am out of
my depth.  Help.

I have seen two classes that get thrown up as HttpServletRequests to the
container.

org.apache.catalina.connector.HttpRequestFacade
org.apache.catalina.core.ApplicationHttpRequest

I assume that these objects should be interchangeable, handed to the
servlet as an HttpServletRequest, treated as an HttpServletRequest.
All I know is that they behave differently from an introspection point
of view--end result being that when you have an
org.apache.catalina.connector.HttpRequestFacade, you can introspect its
get() methods, when you have an
org.apache.catalina.core.ApplicationHttpRequest, you can't.

My environment is Tomcat 4.0.1 running embedded in Jboss.

1.  I get handed a org.apache.catalina.connector.HttpRequestFacade as my
ServletRequest Object.toString().
2.  I expose it as a bean, bean:page and attempt to get the
servletPath property (in other words force a call to
HttpServletRequest.getServletPath()).
3.  This works, as shown below by my ridiculous log-hacking of
PropertyUtils:

[INFO,Default] Matched propertydescriptor to property: servletPath
[INFO,Default] In getReadMethod with PropertyDescriptor servletPath
looking for ReadMethod getServletPath
[INFO,Default] In getAccessibleMethod with method getServletPath
[INFO,Default] org.apache.catalina.connector.HttpRequestFacade is
public.  Cool.

At this point, we got the method and called it, got the property, yadda
yadda.

Let's try that again when our request happens to be a
org.apache.catalina.core.ApplicationHttpRequest:

[INFO,Default] Matched propertydescriptor to property: servletPath
[INFO,Default] In getReadMethod with PropertyDescriptor servletPath
looking for ReadMethod getServletPath
[INFO,Default] In getAccessibleMethod with method getServletPath
[INFO,Default] Didn't succeed elsewhere with getServletPath so let's
check interfaces.
[INFO,Default] In getAccessibleMethodFromInterfaceNest with class
org.apache.catalina.core.ApplicationHttpRequest method getServletPath
parameterTypes: length=0
[INFO,Default] Found 0 interfaces of
org.apache.catalina.core.ApplicationHttpRequest

[ERROR,EmbeddedCatalinaServiceSX] ApplicationDispatcher[/evangeline]
Servlet.service() for servlet jsp threw exception
javax.servlet.ServletException: No getter method for property
servletPath of bean httpservletreq
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContex
tImpl.java:457)
at org.apache.jsp.navbar$jsp._jspService(navbar$jsp.java:626)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServle
t.java:202)
  ...and fifteen more pages of stacktrace.

Basically what is happening is 
A) org.apache.catalina.core.ApplicationHttpRequest is not public, so we
can't use the method
B) For reasons not fully understood, the
getAccessibleMethodFromInterfaceNest can't find any interfaces for
org.apache.catalina.core.ApplicationHttpRequest.  

For a little background, org.apache.catalina.core.ApplicationHttpRequest
extends javax.servlet.http.HttpServletRequestWrapper, which implements
javax.servlet.http.HttpServletRequest, javax.servlet.ServletRequest.
I can't remember if when your superclass implements something, you do
too.

Anyway:  Is this a problem with the PropertyUtils?  Is this an issue
with the ApplicationHttpRequest implementation?  I don't know.  Please
advise.

For reference, my println'ed-up getAccessibleMethod and
getAccessibleMethodFromInterfaceNest are here:

private static Method getAccessibleMethod(Method method) {
System.out.println(In getAccessibleMethod with method  +
method.getName());
// Make sure we have a method to check
if (method == null) {
return (null);
}

// If the requested method is not public we cannot call it
if (!Modifier.isPublic(method.getModifiers())) {
System.out.println(method.getName() +  not public.
Bonking.);
return (null);
}

// If the declaring class is public, we are done
Class clazz = method.getDeclaringClass();
if (Modifier.isPublic(clazz.getModifiers())) {
System.out.println(method.getDeclaringClass().getName() + 
 is public.  Cool.);
return (method);
}
System.out.println(Didn't succeed elsewhere with  +
method.getName() + 
so let's check interfaces.);

// Check the implemented interfaces and subinterfaces
String methodName = method.getName();
Class[] parameterTypes = method.getParameterTypes();
method =
getAccessibleMethodFromInterfaceNest(clazz,
 

Re: Possible bug: Present Struts 1.0 PropertyUtils introspectioncode bonks on the variety of Tomcat 4 ServletRequest facades that get handedto us as HttpServletRequest

2002-01-08 Thread Craig R. McClanahan



On Tue, 8 Jan 2002, James Dasher wrote:

 Date: Tue, 8 Jan 2002 13:18:44 -0500
 From: James Dasher [EMAIL PROTECTED]
 Reply-To: Struts Developers List [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Possible bug: Present Struts 1.0 PropertyUtils introspection
 code bonks on the variety of Tomcat 4 ServletRequest facades that get
 handed to us as HttpServletRequest

 Whoever thought of bean:page, I love it, but it exposes some weird
 introspection inconsistencies in the Tomcat container, and I am out of
 my depth.  Help.


Are you using the 1.0 release of Struts?  If so, you will indeed have
introspection issues.

 I have seen two classes that get thrown up as HttpServletRequests to the
 container.

 org.apache.catalina.connector.HttpRequestFacade
 org.apache.catalina.core.ApplicationHttpRequest


The difference comes from whether your page is accessed directly (you'll
see the first of these) or via a request dispatcher (the second case).

In either case, you should be able to introspect to all public properties.
However, the BeanUtils code that was included in the 1.0 release did have
problems introspecting the public methods that are declared in an
interface (HttpServletRequest) rather than the class itself.  This has
been corrected in the nightly builds (which use the Commons version of
BeanUtils).  Could you give that a try to see if it sovles your problem?

Craig


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Nested tags

2002-01-08 Thread Arron Bates



I could possibly imagine a change to the form tag, but that would be it
wouldn't it?... (yes/no Craig?)

I need to look more at this.

I only mentioned the form tag as I assume you will need to look up the 
forwards  form beans for the action relative to the app/sub-app.

If Resin is not implementing the spec correctly, I'm not interested in
changing Struts to accomodate it.  And don't think I'm picking on just
them - I wouldn't check in the workaround for WebSphere (which didn't
allow deleting request attributes for a while) either.

That's just it. It's implementing it to the letter.
I wont have to tell you what tomcat does :)

Personally, I really want to focus on the controller updates first ...
then, I will look at nested tags.


Sweet.



Arron.


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Building Form Beans from XML Schema?

2002-01-08 Thread Arron Bates

I've tried to do this with Castor generated objects. Problem is though, 
is that the errors are not fine grained at all.
You validate the document by calling the validate() method on the top 
node, and you get a yes or a no.
You can do this for all of the sub objects, but it's just that, you 
still have to implement the field validation yourself.

Naturally you can't play any tricks with the calling of property methods 
to work around various issues as your objects are locked down to the 
automation process.

Otherwise it's quite excellent.


Arron.

Jon Ferguson wrote:

( Republished under appropriate Subject :-( ).

Hey,

I've been toying with the idea of Modelling my form beans using XML Schema,
then generating the actual beans using some XML binding tool like Castor (which
should also generate my validate function).  I should also be able to use
Castor to do RDBMS mapping as well.. (but from a session bean manipulating the
formbeans for example).

I'm thinking of utilising schema from developments such as RosettaNet, BizTalk
Frameworks and ebXML - noting that often the info entered into forms could be
the same message information that might be passed between businesses. (Eg. a
Purchase Order, etc.).

I'm hoping that the result would: a) help to standardize the business app. b)
leave it wide open for making use of b-2-b developments such as webServices and
the above efforts. c) provide automatic form validation (inherent in the
Schema), d) obviate the  hand-coading of formbeans.

Any comments on this approach?  Has anyone tried this?

Cheers,

Jon




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Submission... display:table... tag library

2002-01-08 Thread Jon Ferguson

Ed,

I'm rather new to Struts and taglibs.. however, this seems like a very useful
taglib project.  Table presentation seems to popup everywhere in business app
web development.  The easy sorting ais cool... Its pretty easy to think of
several other features: intable editing, expandable rows,  etc. that might be
useful.  Thanks for your input.

Jon

Ed Hill wrote:

 Hello,

 A few weeks ago, I mentioned in the struts-user list a tag library that we
 are developing which at the time I called gui:table...  I didn't have the
 source ready to go at the time - but rather then trying to get it perfect in
 isolation, I'll risk the public humiliation and go ahead and make available
 what I have now and try to work with others who are interested in
 helping me polish it up.

 Currently, this taglib has a single key tag called table that takes a list
 of objects and displays them as a table.  It has various features
 (alternating row colors, using a decorator for formatting, sorting,
 pagination, etc...)

 My goal over time will be to add other common high-level web display
 patterns to the tag library, for example:

- display:table
- display:tree
- display:tabs
- display:inspector
- etc...

 The source to this tag library is available at:

 http://edhill.its.uiowa.edu/downloads/display.zip

 Examples, showing usage can be found at:

 http://edhill.its.uiowa.edu/display-examples/

 Currently, documentation is little more then just the examples.

 To be honest, my original intention was to donate this taglib to struts if
 there was interest, as we are heavy struts users here at the U of Iowa, and
 I wanted to give back if possible, but there is nothing struts-specific
 about the taglib (other then using some struts-like naming conventions for
 attributes), so it is probably more appropriately a candidate for the taglib
 project, and as such, I have been working on getting the build process for
 the tag working in a jakarta-taglib style.

 I welcome any and all feedback and advice.  If this taglib seems like
 something that would be useful for either struts or taglibs, please let me
 know, and I'll be happy to work with either group to get it put into CVS and
 on a more serious release schedule.

 I am currently being presumptuous, and have the taglib living in the
 org.apache.taglibs.display package, but if this doesn't seem like something
 that would be of use to taglibs, I will certainly change the packaging to
 something more appropriate.

 Thanks.

 -Ed Hill ([EMAIL PROTECTED])
 Software Developer - Information Technology Services - University of Iowa

 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]