glassfish
  1. glassfish
  2. GLASSFISH-15825

Allow user to specify additional metadata while declaratively publishing EJBs to Service Registry

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1_b40
    • Fix Version/s: future release
    • Component/s: OSGi-JavaEE
    • Labels:
      None

      Description

      Allow user to do the following:
      #Exports EJBs with name com.acme.FooEJB and com.acme.BarEJB with additional service properties to the
      Service Registry

      Export-EJB: com.acme.FooEJB; Foo=Bar, com.acme.BarEJB; Foo1=Bar1; Foo2=Bar2

        Activity

        Hide
        TangYong added a comment -

        sahoo, previously, I have commented the following on osgi/cdi draft jira[1],
        [1]:https://www.osgi.org/bugzilla/show_bug.cgi?id=141

        Thinking such a use case, if a user wants to use cdi to export a stateless ejb,
        he/she maybe does the following:

        @Stateless
        @Local(

        {UserAuthService.class})
        @Publish
        public class UserAuthServiceEJB2 implements UserAuthService { ... }

        Then, if using CDI to export a ejb in OSGi, CDI must support exporting or
        registering ejb-related metadata in order to comply with RFP 152 using liking
        "Export-EJB".

        Now, backing to the improvement, "Export-EJB: com.acme.FooEJB; Foo=Bar, com.acme.BarEJB; Foo1=Bar1; Foo2=Bar2" really can be implemented using osgi/cdi enhancement, pl. see GLASSFISH-18972 , maybe should be using the following declaretive way:

        @Stateless
        @Local({UserAuthService.class}

        )
        @Publish({ @property(name="Foo", value="Bar"))
        public class com.acme.FooEJB implements com.acme.Foo

        { ... }

        So, the first thing is to implement GLASSFISH-18972 .

        Show
        TangYong added a comment - sahoo, previously, I have commented the following on osgi/cdi draft jira [1] , [1] : https://www.osgi.org/bugzilla/show_bug.cgi?id=141 Thinking such a use case, if a user wants to use cdi to export a stateless ejb, he/she maybe does the following: @Stateless @Local( {UserAuthService.class}) @Publish public class UserAuthServiceEJB2 implements UserAuthService { ... } Then, if using CDI to export a ejb in OSGi, CDI must support exporting or registering ejb-related metadata in order to comply with RFP 152 using liking "Export-EJB". Now, backing to the improvement, "Export-EJB: com.acme.FooEJB; Foo=Bar, com.acme.BarEJB; Foo1=Bar1; Foo2=Bar2" really can be implemented using osgi/cdi enhancement, pl. see GLASSFISH-18972 , maybe should be using the following declaretive way: @Stateless @Local({UserAuthService.class} ) @Publish({ @property(name="Foo", value="Bar")) public class com.acme.FooEJB implements com.acme.Foo { ... } So, the first thing is to implement GLASSFISH-18972 .
        Hide
        Tom Mueller added a comment -

        Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issue was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.

        Show
        Tom Mueller added a comment - Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issue was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.

          People

          • Assignee:
            Sanjeeb Sahoo
            Reporter:
            Sanjeeb Sahoo
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: