GlassFish Forum | Forum profile

Thank you so much for your time and suggestions. I am almost out of ideas too. Next step to try is to make a standalone java RMI service which will implement the use-cases I would like to have in the EJB. Then simply proxying those methods in an EJB. Implementing my own standalone RMI service would allow me to have all methods synchronize/lock on one object, thus giving me full control and serializing all calls. Cumbersome. Have fun, Jacob.

Thanks a lot! I thought, this two postings have relevances...

I'm using 2.1

I have an application with some non-final static fields. These fields contain default Strings. My application will read new Strings to replace the ones in the static fields when a reload method is called. I have get methods which will return the value of the fields. I would like the reload to replace the old Strings with the new. However, the behavior I'm seeing is when I call the get methods, sometimes I get the old Strings and...

One additional note, if the entity jar is currently packaged as a library jar inside the ear which contains the ejb jar, the library jar needs to be placed in the application library directory of the ear (default is the "lib" from the ear root level) for the library jar to be visible to the component modules.

All I have posted this once already but not as a question so I thought I would try again as a question. At this point, I think there may be a defect/issue but don't want to jump the gun. I am using the Sun One Application Server 8.1. I have a Web Service that is deployed on that app server that accepts Soap requests with attachments. As long as the attachment is small (less than 5 MB in size), everything works fine. However, if the...

Issue 11236 filed. Thanks. > Agree. Can you open an issue: > > * > https://glassfish.dev.java.net/servlets/ProjectIssues > > and add as much as information as you can? We failed > for awhile to > reproduce this issue but your explanation make a lot > of sense. > > A+ > > -- Jeanfrancois

Thanks, I will try it out your advise over the weekend. My home PC still had Netbeans 6.7.1 and Glassfish v2ur2 installed. I will also create and test a Java EE 5 application with the entity in a separate jar and make sure it works on that platform. If it does I wil try to deploy on Glassfish v3-b73 and see what happens. That will help me confirm if the issue is on the Netbeans or Glassfish side. The design pattern I used in the past is...

I have the same problem, but the object being passed is not an Entity, thus does not have any lazy objects. I also disabled Weaving of the class with an aop.xml on all sides...

Any suggestion?