I have a non-Seam component that implements the ServletContextListener interface that is dependent upon Seam components being injected. However, it appears that Seam hasn't fully activated any contexts at the time that my Listener is called from the container.
This is a major problem for me and causes me to question using Seam since I will now have to refactor my previously Seamed components to work in a non-Seam environment...these components are infrastructural in nature (PersistenceFacade, etc) ..so if I have to go through the hassle of constructing them normally, why use Seam?
If anyone has a workaround, this would be great. The @Startup annotation might be helpful, but it only guarantees construction, not execution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127098#4127098
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127098
anonymous wrote : I said that because, I don't think anyone can really answer that except the stewards of Seam. All other answers will be pure speculation. I was just supporting your question.
|
| I am beginning to think that there should be a warning not to put any SFSB as Session scope or higher due to memory consumption.
I am sorry I misunderstood.
Anyways my use case was not allowing me to use SESSION context in. I have done it using param.
Thanks a lot all.
-Vivek
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127097#4127097
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127097
I can see the problematic code in RemotingConnectionImpl createRemotingMetaData:
populateHeaders(reqMessage, metadata);
| clientConfig.put("chunkedLength", "1024");
| if(msgContext != null)
| {
| Properties epmdProps = msgContext.getEndpointMetaData().getProperties();
| String chunkSizeValue = epmdProps.getProperty("http://org.jboss.ws/http#chunksize");
| int chunkSize = chunkSizeValue == null ? -1 : Integer.valueOf(chunkSizeValue).intValue();
| if(chunkSize > 0)
| {
| clientConfig.put("http://org.jboss.ws/http#chunksize", chunkSizeValue);
| } else
| {
| clientConfig.remove("chunkedLength");
| }
| }
It automatically puts the chunkedLength property in place any only removes it if there is a MessageContext (non null) and that MessageContext does not have the EndPointMetaData property for chunking. The only problem is that if I'm just doing a simple SOAPMessage with a URL endpoint, I don't have a MessageContext and this code gets skipped. Heiko, any thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127091#4127091
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127091