Devsphere Mapping Framework

www.devsphere.com

Devsphere Mapping Framework provides an application
programming interface (API)
that allows you to map objects to HTML forms, XML
documents and property text
streams. The mappings are bi-directional. You can fill
the properties of a bean
object with the HTTP request parameters whose values
were gathered using an HTML
form. You can also set the default values of a pure
HTML form to the data
contained in a bean object. A bean object can be
converted to a text / XML
document and vice-versa.

The most interesting feature is the ability to take a
pure HTML form and insert
the values of the proprieties of a bean object into
the HTML form as the default
values of the form elements. This operation is done
automatically and it helps
you to return a partially filled form to the user's
browser without having to
mix Java and HTML code. You use pure HTML forms and
pure Java.

We provide a Developer's Guide, API Documentation,
helpers (utility classes),
many examples (HTML based table editor, image map
handler, file uploading,
internationalized app) and a full distributed
application based on JavaMail and
standard protocols (HTTP, SMTP, POP3, IMAP).


Benefits of Using the Framework

1. Architectural benefits

Devsphere Mapping Framework
    * supports an application model that makes a clean
separation between bean
processing, form generation and data handling. This is
similar to the MVC model.
    * extends the JavaBeans model (without altering
it) with concepts specific
to form processing, such as optional properties,
default values and error
messages.
    * brings object oriented features, such as
inheritance, containment and
aggregation into the form processing domain.
    * allows you to build easily internationalized Web
applications. The I18N
support exists in the application model and is
extended by the framework's API.


2. Development benefits

Devsphere Mapping Framework
    * frees Web Application Developers of the routine
tasks (such as form data
handling, user error handling and dynamic form
generation) and let them focus on
the business logic (bean object processing).
    * is easy to use and reduces significantly the
development time. Existent
beans and HTML forms don't need any changes. The only
requirement is the use of
the same names for bean properties and form elements.
    * reduces the maintenance costs. The application
model separates the
components of the applications in five categories:
data beans, bean resources,
forms, handlers and processors.
    * maps beans to XML and text simplifying the
building of software that needs
messaging (such as B2B applications) and
XML/text-based persistence (such as
Web-based administration utilities).


3. Testing benefits

Devsphere Mapping Framework
    * splits the mapping errors in two categories:
user errors (like "missing
data" and "number format error") and application
errors. For example, an
application error may occur when there are no form
elements with the name of a
bean property. In this case, the bean property cannot
be mapped. The "missing
form element" error would be inserted at the beginning
of the HTML form that is
sent through the servlet's output stream. To correct
the error, the developer
would have to edit the HTML file and add the form
element.
    * reloads the cached HTML forms after they are
modified. This avoids the
restarting of the application and is much faster than
recompiling a JSP page.
    * includes an extensible logging mechanism which
provides loggers that wrap
print streams and servlet contexts. You may define new
loggers that suit the
needs of your application.


4. Deployment benefits

Devsphere Mapping Framework
    * is very fast and doesn't need too much memory.
For HTML parsing, it uses a
custom parser highly optimized for forms. Pure HTML
files can be parsed only
once and cached in memory. Of course, you may control
which forms are cached and
which of them aren't. For XML parsing, the framework
uses the SAX API.
    * may run in any servlet engine / application
server based on the Servlets
2.x API using any JDK/JRE version (except the old JDK
1.0). If the servlet
engine supports Java Server Pages, the JSPs can take
full advantage of the
framework's API.
    * may also run outside of a servlet engine /
application server, in the
absence of the Servlet API. For example, a standalone
application that does
offline processing could use the framework to convert
text / XML documents to
bean objects.


You can download the evaluation version now and order
the product later.

We offer professional consulting services and customer
support. Please contact
us for details.

www.devsphere.com



__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to