| @Transactional
| public boolean isManaged()
| {
| return getInstance()!=null &&
| getEntityManager().contains( getInstance() );
| }
|
getEntityManager().contains( getInstance() ) is returning false is the culprit.
So I checked whether the EM has changed by looking at the hash code (is this a valid way of doing it?), and the hash codes remain constant throughout the conversation. As well, the (T) getComponentInstance( getPersitenceContextName() ) is only called once, which is expected, so it doesn't appear the EM is ever null.
The getInstance() hasn't changed either--it's not null.
Is there anywhere in Seam where em's cache is cleared either explicitly or implicitly?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055410#4055410
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055410
Hi,
We are using JBoss WS 1.2.1 in our server side.
Our client side is implemented in Flex and it communicates with the server side through JBoss WS.
Flex can?t not handle a WebFault that gives HTTP status code = 500.
Therefore, we are looking for a way that we can change HTTP status code from 500 to 200 when throwing an exception.
Would be very appreciated if you can shed some light how to change HTTP status code from 500 to 200.
Use a handler, servlet, ?
Thanks,
James
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055408#4055408
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055408
| /**
| * Load a factory using this ordered lookup procedure
| *
| * <ol>
| * <li>Use the system property
| * <li>Use the properties file "lib/jaxm.properties" in the JRE directory
| * <li>Use the Services API (as detailed in the JAR specification), if available, to determine the classname
| * <li>Use the default factory implementation class
| * </ol>
| *
| * @author Thomas.Diesler(a)jboss.com
| * @since 14-Dec-2006
| */
| public class SAAJFactoryLoader
|
Step 3, the Services API uses a classloader. You should probably be able to set the context classloader such that it gives access to the SAAJ impl that you want.
Please note, JBossWS will only work with its own SAAJ impl.
Please use the jbossws-2.0 code base
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055395#4055395
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055395