[jspies2]

Hey Scott - Sorry this took so long, I've been travelling this week.  Log attached.  Please let me know if I can do anything else.

[smarlow]

Thanks Jason!  The updated trace log output was very helpful.  I created a new jira for this issue (WFLY-3531).

[smarlow]

Hi Jason,

Can you grab my potential fix and see if it helps?   I think the following will you get the new GIT branch, which you should be able to build (note the build output is different now, see dist folder for older style).

git fetch https://github.com/scottmarlow/wildfly.git WFLY-3531_pu_next_phase_deps:WFLY-3531_pu_next_phase_deps

git checkout WFLY-3531_pu_next_phase_deps

[jspies2]

Hey Scott, thanks!  I'll try this tomorrow and let you know.  For some reason I stopped getting notifications from the community and I just checked back on chance.

[smarlow]

Jason, I stopped getting notifications also.  So its not just you.  I'll report that forum notifications are broken.

Scott

[jspies2]

Scott-

Thanks!  This works as expected.  No errors and everything seems correctly weaved.  We've decided to license EAP, so this doesn't help us near term but hopefully it helps others and helps us when EAP 7 comes out.

[smarlow]

Jason,

Thanks to you as well for all of your help!  EAP users can ask for the (WFLY-3531) fix as a one-off or to be included in the maintenance stream.

Scott

[jspies2]

Scott - Is this bug fix something that can be made to work with EAP and Eclipselink?  I know eclipselink can be made to work with EAP/JBoss 7 as outlined in the guide, but wasn't sure if this bug fix required any of the new jipijapa stuff in wildfly or if it was something that could be made to work with however eclipselink worked with the older jboss.

[smarlow]

Jason,

At the moment, I see no reason why the fix could not be back ported to EAP.  The fix does not need anything new from jipijapa or wildfly.  If you or any EAP users would like the fix, please open a ticket with our support organization and they should be able to help. 

Best,

Scott