FYI.. Jesper's comments from a separate thread.. ---------------------------------------------------------------------------------- Hi. Some comments for subject... General: -------- 2) JBoss AS Embedded is not a truely embedded platform - it is a library which points to an existing JBoss AS installation. Main focus for the project is that developers should be able to run their unit tests. 3) JBJCA/Embedded is not tied to the JBoss AS 6 release - its a standalone project. So hopefully it'll be GA before AS 6. Connectors: ----------- 8) Look into having your own MC beans - deployed through a teiid-server-jboss- beans.xml file 11) Check to see if @ManagedObject could fit this gap 12+13) You can place JAR archives in server/teiid/lib - and they will be available to the entire server configuration Engine: ------- 17) If JBoss AS is the main platform - I would go with the teiid-server-jboss- beans.xml file again Admin API: ---------- 34) Profile Service and @ManagedObject should be Blocker requirements in my book - having your own management layer is not going to work. It looks like you are on the right path :) Drop by the various user forums to ask additional questions. Best regards, Jesper

Jesper's Response.. ----------------------------------------------------------------------------------- Hi Ramesh. On Wednesday 21 October 2009 18:15:20 Ramesh Reddy wrote: Its J*e*sper ;) post these on WIKI page to share with others. Feel free, we should have this discussion on the Teiid design forum really... > (2) I understand. In Teiid we call this mode as embedded "File-path > profile" in current release. We have to sacrifice the > "classpath-profile" now for the benefits. see > https://www.jboss.org/community/wiki/ConnectingtoTeiidEmbedded Ok. People have different definitions of embedded ;) for > Teiid. Then, how are these available through JMX? Different concepts. A MC bean is just a Plain Old Java Object (POJO) managed by the JBoss Microcontainer. The MC projects provides various APIs/SPIs to do integration. http://www.jboss.org/index.html?module=bb&op=viewforum&f=228 Lead: Ales Justin Profile Service handles "profiles" of a server -- e.g. "give me a configuration with logging, naming, transaction, jca, messaging and ejb3". The profile service selects the MC beans that will provide such a profile. http://www.jboss.org/index.html?module=bb&op=viewforum&f=160 Lead: Emanuel Muckenhuber (and Scott Stark) @ManagedObject identifies POJOs which have a management view - they don't have to be registered as MC beans. http://www.jboss.org/index.html?module=bb&op=viewforum&f=160 Lead: Emanuel Muckenhuber (and Scott Stark) @ManagedObject <-> MBean is handled by a 'bridge'. http://www.jboss.org/index.html?module=bb&op=viewforum&f=160 Lead: Emanuel Muckenhuber (and Scott Stark) You'll need various layers to deal with container (and kernel) specific details - in order to run on various EE servers. > Can you explain your comments on (34)? When Teiid is running as part of the JBoss Application Server it should use Profile Service) Create the server configuration for the Teiid platform @ManagedObject) To identify management objects Other servers uses other mechanisms. You'll have to evaluate each technology before you bring it in - "do I want a hard dependency on this project ?", "do the project have the performance profile we need ?", ... Good idea is to use http://jboss.org/tattletale/ to get an overview of the projects you are working with - yes, that was a shame-less plug ;) I keep the documentation for JBJCA up-to-date for each release here: http://docs.jboss.org/jca/ But *note*, that certain parts of JBJCA != JBossAS... and there is still development to do before the first stable release.