Announcement Announcement Module
Collapse
No announcement yet.
Grails 2 running in STS and deploying war to tomcat yield different runtime results Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Grails 2 running in STS and deploying war to tomcat yield different runtime results

    We now have run into issues twice where code works fine running with the tomcat plugin within STS and breaks when built and deployed to tomcat outside. This is a SEVERE issue for us as we have had 2 releases jeopardized now.

    The first issue was a transientobjectexception seen only when executing in tomcat stand alone. We worked around that fairly easily.

    The second is with the use of a command object and the lazylist. It seems the lazylist instances are created but then the attributes are not. This is what the form data looks like:
    expandableDeptCourses[0].courseId:337158
    expandableDeptCourses[0].termNumber:2
    expandableDeptCourses[0].allocation.id:4183
    expandableDeptCourses[0].selected:true
    expandableDeptCourses[1].courseId:337765
    expandableDeptCourses[1].termNumber:2
    expandableDeptCourses[1].allocation.id:
    expandableDeptCourses[1].selected:false

    In STS each expandableDeptCourses has all 4 attributes populated. In tomcat standalone the instances are created but the properties are not. Null exceptions resulted. Working around this is not easy and time consuming causing us to miss our release date..

    Things working differently in Grails 2 is fine but when I am running Grails 2.0.3 and tomcat 7 with the plugin within STS and then we build a war with Grails 2.0.3 and deploy to tomcat 7 standalone and things do not work the same that is not workable.

    Does anyone have any info on this?
Working...
X