tag:blogger.com,1999:blog-35481627.post6008201870818985398..comments2023-06-11T09:40:41.556+02:00Comments on The Netbeans Experience: Anonymoushttp://www.blogger.com/profile/01088795596952787822noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-35481627.post-13174662630816179082007-07-09T22:18:00.000+02:002007-07-09T22:18:00.000+02:00Hmmm, maybe I should try the M9 build again. What ...Hmmm, maybe I should try the M9 build again. What you can do to get it to work is create a new EJB project, deploy it and then copy your project over the new project and it works in about 99% of the cases. At least that is my experience. The problem is that you need to do this every time something is wrong in your app and you get the pool problem again.<BR/><BR/>IwanAnonymoushttps://www.blogger.com/profile/01088795596952787822noreply@blogger.comtag:blogger.com,1999:blog-35481627.post-55176134061698290372007-07-09T15:47:00.000+02:002007-07-09T15:47:00.000+02:00I also have some problems with NB6M10+GlassfishV2....I also have some problems with NB6M10+GlassfishV2. Everything worked fine with NB6M9+GlassfishV2. After update to M10 my application doesn't deploy anymore. It always says that the connection pool isn't registred with the environment or something like that. I tried to create a completely new EJB-Module with the same results. The funny thing is, that it deploys fine on Glassfish v1 it even deploysAnonymousnoreply@blogger.com