HP3000-L Archives

July 2003, Week 2

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
OT: Looking for feed back on Java/JSP tags
From:
Evan Vaala <[log in to unmask]>
Reply To:
Evan Vaala <[log in to unmask]>
Date:
Thu, 10 Jul 2003 12:40:10 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (75 lines) 
Just looking for some Java/JSP feedback from any people working with it out
in 3000L.

(Following contains tags - hope they are translated to lt gt.  If not I
will resend translated.)

Thinking in the mindsets of an HTML developer and of an application
developer.

I have a tag (bean) with similiar functionality to the jsp:usebean tag, but
with a few more capabilities.

Do you think the html coder would like to work with the multiple "bean"
tags, much like the usebean tags defined within their html?

<body>
<ra:bean id="myBean1" class="ra.apps.model.MyBean1" scope="session" />
<ra:bean id="myBean2" class="ra.apps.model.MyBean2" scope="request" />
<ra:bean id="myBean3" class="ra.apps.model.MyBean3" scope="event" />

<%=myBean1.getStuff()%><br>
<%=myBean2.getStuff()%><br>
etc...

</body>

Or would they prefer to have these beans defined in a seperate application
xml config file that the application developer controls.

app.config.xml:

<config>
    <screen name="myscreen.screen">
        <bean id="myBean1" class="ra.apps.model.MyBean1" scope="session" />
        <bean id="myBean2" class="ra.apps.model.MyBean2" scope="request" />
        <bean id="myBean3" class="ra.apps.model.MyBean3" scope="event" />
        <other-screen-atts />
    </screen>
</config>


The html developer would only be concerned with one tag:

<body>

<ra:definebeans screen="myscreen.screen" /> <!-- defines myBean1, myBean2,
myBean3 -->

<%=myBean1.getStuff()%><br>
<%=myBean2.getStuff()%><br>
etc...

</body>

The latter option as I mentioned before gives more control to the
application developer, who is probably the person who will be putting the
myBeanX objects inside the various scopes.

All the html developer has to be concerned with is working with the beans
and not having to define them.  Also the HTML developer would not be able
to mistakenly change the bean defs.

Just looking for feedback from a pretty open minded community.

I know that I could get alot of feedback from the Java/JSP communities, but
such topics can sometimes cause a list meltdown.  Just trying 3000L first.

Thanks!

Evan Vaala
Rockwell Automation

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2