Ramesh, Up until now, Van and I were under the impression that Teiid discovery in 6.3 for Jopr (Teiid Console) may and likely WOULD change, but the core functionality made available through the Admin API would not. Based on this thread it sounds like both discovery and configuration will be completely different. Instead of doing a lot of work on the console that will get tossed, we need to put the Teiid console development on hold until all the design decisions are made regarding deployment and configuration of Teiid for 6.3. We need to be included in any decisions made regarding the final approaches. Also, Van and I can be used as resources for implementing the configuration approach which will allow us to more easily add the necessary hooks to the Teiid Jopr plugin. Thanks, Ted ----- Original Message ----- From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; To: teiid-dev(a)lists.jboss.org Cc: teiid-designer-dev(a)lists.jboss.org Sent: Thursday, October 22, 2009 9:19:46 AM GMT -06:00 US/Canada Central Subject: Re: [teiid-dev] Teiid In JCA Container 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. _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev