glassfish
  1. glassfish
  2. GLASSFISH-16164

eclipselink.weaving breaks marshalling out of the box

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1_b43
    • Fix Version/s: None
    • Component/s: entity-persistence
    • Labels:
      None
    • Environment:

      Windows 7 and Mac OS X

      Description

      Separately deployed EJB components that return @Entity objects, fail serialization and return empty objects to remote components (such as a managed bean in a separately deployed WAR). Adding: <property name="eclipselink.weaving" value="false"/> to persistence.xml fixes the issue, but cant be expected behavior out of the box. I tried 2 separate clean installs, and an upgrade from 3.0.1 but all have same broken behavior.

      To reproduce:
      1) Deploy EJB jar with a stateless EJB that returns an entity from remote interface.
      2) Deploy web application with a managed bean that retrieves entity from injected EJB
      3) Access managed bean from view.

      I get empty entity classes (all fields null) with no errors in server.log.

      I have a test case intellij project illustrating issue if required.

        Issue Links

          Activity

          Hide
          dmitriy.balakin added a comment -

          I use eclipselink-staticweave-maven-plugin as a workaround.

          Show
          dmitriy.balakin added a comment - I use eclipselink-staticweave-maven-plugin as a workaround.
          Hide
          markokanala added a comment -

          Has anyone tried if static weaving at the remote and calling side is a workaround ?

          see http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance/Weaving/Static_Weaving

          Show
          markokanala added a comment - Has anyone tried if static weaving at the remote and calling side is a workaround ? see http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance/Weaving/Static_Weaving
          Hide
          vins4java added a comment -

          I agree with eldiegos. I found this bug up to lastest 3.1.2.2 and there's no way to know if it will be fixed for glassfish 4.0 or not...
          What's the plan for the resolution of this bug?

          Show
          vins4java added a comment - I agree with eldiegos. I found this bug up to lastest 3.1.2.2 and there's no way to know if it will be fixed for glassfish 4.0 or not... What's the plan for the resolution of this bug?
          Hide
          eldiegos added a comment -

          OMG. This bug has been a pain on the neck until i found this issue. What a waste of time trying to solving it. Please glassfish team solve it.

          I have vote for it.

          Thanks.

          Show
          eldiegos added a comment - OMG. This bug has been a pain on the neck until i found this issue. What a waste of time trying to solving it. Please glassfish team solve it. I have vote for it. Thanks.
          Hide
          chrispy added a comment -

          This bug is still a problem. When will this be fixed? A workaround is not a solution :-/

          Show
          chrispy added a comment - This bug is still a problem. When will this be fixed? A workaround is not a solution :-/

            People

            • Assignee:
              Harshad Vilekar
              Reporter:
              netricsoft
            • Votes:
              22 Vote for this issue
              Watchers:
              23 Start watching this issue

              Dates

              • Created:
                Updated: