Since this is a JBoss list, it seems
appropriate for advertising
JBoss services and not appropriate for
non-JBoss related services.
Seems like a
reasonable place to draw a line.
JD
-----Original Message-----
From: Gary S. Cuozzo [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 7:28 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] [ANN] Tammi 1.0 Released - a JMX Application Framework
You are not the only one. I totally agree
with you. But, JBoss Group LLC uses this list (and the dev list) to
advertise their training and other services. So, where does the line get
drawn? What is ok for one, should be ok for all. This has bothered
me for some time now.From: Gary S. Cuozzo [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 7:28 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] [ANN] Tammi 1.0 Released - a JMX Application Framework
gary.
Andreas Mecky wrote:
Hi,maybe I am the only one but I don't think that this is the right place for this kindof shameless self commercial.Or if nobody else agrees then I can also start using JBoss as my mailing listfor my open source projects?WBRAndreas----- Original Message -----From: Marketta PrihaSent: Monday, February 03, 2003 11:18 AMSubject: [JBoss-user] [ANN] Tammi 1.0 Released - a JMX Application FrameworkHello
This message is relevant to JBoss users interested in applying JBoss' JMX capabilities also in servlet development and business logic implementation.
The Norther Organization has released Tammi 1.0 open source development framework for web applications at http://tammi.sourceforge.net/. Downloads, a demo with an on-line manual, extensive tech spec and API docs are available.
Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.
The key technologies applied include service proxy architecture with Java Management Extensions (JMX), dynamic configuration with Dynamic Java, MVC filters and filter chains with Java Servlets, template processing with Apache Velocity and Freemarker, and general design derived from Apache Turbine. The architecture allows effortless integration of additional libraries when needed.
Tammi, as well as applications built with it, can be executed either as a servlet or filter chain under a J2EE compatible servlet container, the recommended approach for JBoss users. In addition, it contains an internal HTTP(S) 1.1 capable connector with competent performance.
Separate notes on how to build and deploy Tammi to JBoss are in Sourceforge under Docs-section.
http://sourceforge.net/docman/display_doc.php?docid=15052&group_id=62554
Tammi application components are JMX MBeans meant for implementing independent business logic themselves or to act as proxies to native libraries, remote programs and other kinds of manageable systems.
In Tammi, we have chosen to exploit a template engine instead of JSP. The localization and customization of look-and-feel, as well as the RAD support for HTML forms, is based on that approach.
Tammi implements an MBean administration interface with templates. Under JBoss you'll have two options for administration: the JMX Console and Tammi administration pages. In both interfaces, you can view all the MBeans in the JBoss and Tammi domains.
Regards,
Marketta
mpriha at users.sourceforge.net
<http://sourceforge.net/sendmessage.php?touser=478080>