Details

      Description

      Would love to get your thoughts on this. We are currently refactoring our code to have publicly available -api jar files that contain POJOs and Rest Service interfaces. So that we can use these classes ourselves, they are annotated with @Portable, @Bindable, and @Remote as appropriate.

      We would like to NOT have to include all the Errai dependencies, but rather have a single annotation dependency. This would make it cleaner from a dependency standpoint, and would even allow us to easily create a fatjar as an option.

      Does this make sense?

      Another option would be to use ErraiApp.properties to map @Portable, @Bindable and @Remote to annotations contained within the jar (@MyPortable, @MyBindable, @MyRemote) - this would allow toe jar to only depend on Jaxb/Jaxrs

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mbarkley Max Barkley
                Reporter:
                jblinick Josh B
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: