dev@glassfish.java.net

Re: [金山毒霸识别此邮件为垃圾邮件] Re: Untified description for Component

From: liao <obframework_at_21cn.com>
Date: Fri, 14 Sep 2007 07:23:33 +0800

Lloyd,



Ok,I will give you more detail about it.





Chris



  ----- Original Message -----
  From: Lloyd L Chambers
  To: dev_at_glassfish.dev.java.net
  Sent: Friday, September 14, 2007 1:16 AM
  Subject: [金山毒霸识别此邮件为垃圾邮件] Re: Untified description for Component


  Chris,


  What's the problem that needs solving? How is it not solved by existing APIs in GlassFish?


  I understand you have a solution. But I don't understand the issue you propose to solve, its use cases and intended users, etc. Please explain the background; the solution comes later.


  Lloyd


  On Sep 11, 2007, at 6:19 PM, liao wrote:


    Lloyd,


    There are some kinds of services in J2ee domain? For example: EJB service, Datasource service and so on, and some

    components live in these service domain. The following table will describes the mapping relationship between service

    and component.

          Service Component
          JDBC Service Datasource component
          EJB service EJB component(session.entity message bean)
          POJO service POJO component
          RMI service RMI component

    ………………………………………………………………………………………..


    All of the right column in the above table are components, which is a common featuer.It is right?

    We can use a common way to describe it? So I designed a XML format for it,a demo is below:


    <component id ="firstSource" type="Datasource">
       ........................................

    </component>

    notes:
      id: component ID
      type: component type


    The format looks very simple? Is similar to POJO description in IOC? Yes,In fact,I regard POJO Bean as a kind of simple

    component.Different component,different description, you can define more detail for a component below component tag.

    Commonly,we use containers to manage components in J2ee domain,include components'description. We can regard description

    of a component as another useful object ? This is a core thinking in my server,I will send some introduction documents

    about my server for referrence.Please save the attatchment to your local and click index.html file from the pressed file.

    Thanks!





    Best regards


    Chris Liao







































      ----- Original Message -----
      From: Lloyd L Chambers
      To: dev_at_glassfish.dev.java.net
      Sent: Wednesday, September 12, 2007 7:28 AM
      Subject: [金山毒霸识别此邮件为垃圾邮件] Re: Issue 2394


      Liao,


      Not yet. You haven't told me what is compelling and why I (or someone else) should spend the time.


      To "sell" your idea, I want to hear what problems you propose to solve. So far I don't understand what those problems are. If there is a clear and concise proposal detailing the issues to be addressed and the proposed solution, please send it to me directly, and I'll take a look.


      Lloyd


      On Sep 11, 2007, at 4:31 AM, liao wrote:


        Hi Lloyd,


        You have run my server and read some documents from the server?





        Chris Liao


          ----- Original Message -----
          From: Lloyd L Chambers
          To: dev_at_glassfish.dev.java.net
          Sent: Tuesday, September 11, 2007 7:51 AM
          Subject: [金山毒霸识别此邮件为垃圾邮件] Re: Issue 2394


          Chris,


          From where do you get the term "management component"? Is it a term you're inventing, or something that has been defined elsewhere?


          ===> Have you read the AMX documentation so we can talk a common language about the management interface of GlassFish?


          Lloyd


          On Sep 10, 2007, at 4:36 PM, liao wrote:


            Lloyd,
            Â
            Â
            Â
            I want to address management components(MComponent),which are similar to management bean(MBean). In my eyes,
            Â
            a MComponent should work as a bigger unit than a management bean.It maybe consists of more than one class instance,
            Â
            For example: EJB2.0 component,which is consists of a home, a remote, a bean,it is right? We can regard MBean as a kind of
            Â
            Components? Do you accept this point?  But how to describe components? I want to look for a unified format for them.
            Â
            Those xml segments which were contained in my previouse are my sample.
            Â
            Â
            Â
            Â
            Â
            Chris liao
            Â
            Â
            Â
            Â
            Â
            Â
            Â
              ----- Original Message -----
              From: Lloyd L Chambers
              To: dev_at_glassfish.dev.java.net
              Sent: Tuesday, September 11, 2007 12:34 AM
              Subject: [½ðɽ¶¾°Ôʶ±ð´ËÓʼþΪÀ¬»øÓʼþ] Re: Issue 2394


              Liao,


              What problem exactly are you trying to address?  I think this would be better written up in an HTML or PDF format. ÂÂ


              Have you read the AMX documentation? That is our current MBean API for public use.


              https://glassfish.dev.java.net/javaee5/amx/index.html


              Lloyd


              On Sep 9, 2007, at 8:26 PM, liao wrote:


                2394










    <Introduction.zip>
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
    For additional commands, e-mail: dev-help_at_glassfish.dev.java.net