  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | JSP - A mailing list about Java Server Pages specification and reference | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Recognising j2ee patterns through the j2ee management model | Recognising j2ee patterns through the j2ee management model 2004-02-04 - By Jeremy Pitten
Back Having recently digested the second addition of Core J2EE Patterns I'm wondering if the JSR-77 (See http://JSR-77.ora-code.com) J2EE Management Information Model will be extended to support/give visibility of such items as Intercepting Filters, POJOs and DAOs.
How are these components managed at the moment? Are there any vendor specific extensions that recognise these components as managedObjects?
Are these component types considered to be not worth managing (I hope so), or is it that we don't yet know how to specify how to manage them?
Does anyone have any views as to how these components should be managed?
Is anyone aware of any move to enhance/extend JSR-77 (See http://JSR-77.ora-code.com)?
Why am I asking? I've been developing a tool that is trying to visualise architectural design patterns using nothing but a MEJB dialogue to build a picture of a deployment.
regards,
Jeremy
www.jpitten.btinternet.co.uk
==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1"> <META content="MSHTML 6.00.2600.0" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2><FONT face=Arial size=2>Having recently digested the second addition of Core J2EE Patterns </FONT></FONT><FONT face=Arial size=2><FONT face=Arial size=2>I'm wondering if the JSR-77 (See http://JSR-77.ora-code.com) J2EE Management Information Model will be extended to support/give visibility of such items as Intercepting Filters, POJOs and DAOs.</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2></FONT></DIV><FONT face=Arial size=2></FONT> <DIV>How are these components managed at the moment? Are there any vendor specific extensions that recognise these components as managedObjects? </DIV> <DIV> </DIV> <DIV>Are these component types considered to be not worth managing (I hope so), or is it that we don't yet know how to specify how to manage them?</DIV> <DIV> </DIV> <DIV>Does anyone have any views as to how these components should be managed?</DIV> <DIV> </DIV> <DIV>Is anyone aware of any move to enhance/extend JSR-77 (See http://JSR-77.ora-code.com)?</DIV><FONT face =Arial size=2> <DIV> </DIV> <DIV>Why am I asking? I've been developing a tool that is trying to visualise architectural design patterns using nothing but a MEJB dialogue to build a picture of a deployment.</DIV> <DIV> </DIV> <DIV>regards,</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>Jeremy</FONT></DIV> <DIV> </DIV> <DIV> <A href="http://www.jpitten.btinternet.co.uk">www.jpitten.btinternet.co.uk</A>< /DIV> <DIV></FONT> </DIV></BODY></HTML> ==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
 |