|
Hello, Guys!
I'm working with: - Flex 4 - Grails 1.3.7 - plugin Blazeds-2.0 (used to integrate the Flex project with Grails project) The BlazeDS plugin receive de request from the Flex through the BlazedsOpenSessionInViewFilter class. During its flow, after the execution of all the code, when the Hibernate try commit the manipulations, I get a NullPointerException in this line: if (!FlushMode.MANUAL.equals(sessionHolder.getSession().getFlushMode())) Because the previous line: SessionHolder sessionHolder = (SessionHolder)TransactionSynchronizationManager.getResource(sessionFactory); Don't retrieve the SessionHolder... so it's null... Someone know why it happen and the form to correct the problem? * You can see a picture showing the problem attached. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
2012/6/14 Joelson Lucena
> Hello, Guys! > > I'm working with: > > - Flex 4 > - Grails 1.3.7 > - plugin Blazeds-2.0 (used to integrate the Flex project with Grails project) > Out of interest, are you using Grails 1.3.7 because of an external requirement or because BlazeDS doesn't work with Grails 2.0? From time to time I see a question about the BlazeDS plugin on this list and they don't tend to get answered. I think that plugin has been abandoned. From what you can see at https://github.com/grails-plugins/grails-blazeds it underwent major work at the end of 2010 and since then nothing happened. If GraniteDS is an option you could look into that. The GDSFlex plugin works with Grails and is sporadically maintained. Which is better than the BlazeDS one. It finally got upgraded to Grails 2.0 last month, but you have to download the sources from GitHub at the moment because the updates haven't been published yet. John --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Exactly!
I'm using this version just because of the compatibility between the Grails version and the plugin version. I really had thought about change to the Granite plugin before, but as I'm working for a company, I prefered wait for another position from someone who had passed the same problem. Thank You! See you! 2012/6/15, John Fletcher <[hidden email]>: > 2012/6/14 Joelson Lucena >> Hello, Guys! >> >> I'm working with: >> >> - Flex 4 >> - Grails 1.3.7 >> - plugin Blazeds-2.0 (used to integrate the Flex project with Grails >> project) >> > > Out of interest, are you using Grails 1.3.7 because of an external > requirement or because BlazeDS doesn't work with Grails 2.0? > > From time to time I see a question about the BlazeDS plugin on this > list and they don't tend to get answered. I think that plugin has been > abandoned. From what you can see at > https://github.com/grails-plugins/grails-blazeds it underwent major > work at the end of 2010 and since then nothing happened. > > If GraniteDS is an option you could look into that. The GDSFlex plugin > works with Grails and is sporadically maintained. Which is better than > the BlazeDS one. It finally got upgraded to Grails 2.0 last month, but > you have to download the sources from GitHub at the moment because the > updates haven't been published yet. > > John > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
2012/6/15 Joelson Lucena <[hidden email]>:
> Exactly! > > I'm using this version just because of the compatibility between the > Grails version and the plugin version. > > I really had thought about change to the Granite plugin before, but as > I'm working for a company, I prefered wait for another position from > someone who had passed the same problem. > > Thank You! > See you! The ironic thing about DS and companies is that BlazeDS was the more official one, but now Adobe has abandoned Flex so I guess it's kind of in limbo. Meanwhile GraniteDS was the small third-party one, but last year they launched a proper company with a complete support offering. So from a support point of view Granite is probably better now! Anyway, good luck. John --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Powered by Nabble | Edit this page |
