[JBoss Seam] - Re: How many EntityManagers and SFSBs in a web app?
by SmokingAPipe
Gavin, I'm not trying to yell stupid things. PHP is clearly a stupid thing. It doesn't suffer LIEs because it's so primitive it doesn't have any abstraction for access to the DB at all. No (real) objects to initialize means no initialization errors, and applications which are messes of procedural code and no separation of view and logic. It does have a very simple and effective way of managing DB connections, but it's incapable of going to the next generation of web services, which is what Seam is for.
Not using conversation scope is obvoiusly where I'm messing myself up. I didn't understand this. I need to either figure out if Tomahawk can work with Seam and maintain conversation, or just ditch Tomahawk, as cool as some of the Tomahawk stuff is.
anonymous wrote : . I think it is fair to say that you should, in most normal apps, only need to store one entity in the session scope - the logged in user - and I've never had to place any in the application context.
Ok, that's a useful bit of info.
As for SMPC in Conversation scope: So I should change my SFSBs to be conversation-scoped (as you're saying). I should also remove the EXTENDED PersistenceContext parameter? If my SFSB is Conversation scope, I just don't have to worry about it?
As a corollary, if I do all that, and test it with a Tomahawk component, and it breaks, well, I just take out the Tomahawk stuff until they come out with a version that works with Seam.
Is this the right track?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992157#3992157
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992157
19 years, 4 months
[JBoss Messaging] - Re: Exception by getting a reference to the ConnectionFactor
by BjoernWilken
Hey Tim!
The Client is a Program running from Exclipse, that means a stand alone Client. You are right, i didn't include the jboss-messaging-client.jar.
Now i have included the jboss-messaging-client.jar.
But I got a new Exception:
java.lang.RuntimeException: Failed to config client side AOP
at org.jboss.jms.client.JBossConnectionFactory.ensureAOPConfigLoaded(JBossConnectionFactory.java:251)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:196)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:96)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:91)
at Client.main(Client.java:49)
Caused by: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.io.EOFException
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:306)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
at org.jboss.remoting.Client.invoke(Client.java:525)
at org.jboss.remoting.Client.invoke(Client.java:488)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.invoke(ClientConnectionFactoryDelegate.java:199)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$getClientAOPConfig_8697532701842707646.invokeNext(ClientConnectionFactoryDelegate$getClientAOPConfig_8697532701842707646.java)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.getClientAOPConfig(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.JBossConnectionFactory.ensureAOPConfigLoaded(JBossConnectionFactory.java:233)
... 4 more
Caused by: java.io.EOFException
at java.io.DataInputStream.readByte(Unknown Source)
at org.jboss.serial.io.JBossObjectInputStream.readByte(JBossObjectInputStream.java:225)
at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:411)
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
... 11 more
Hum?
Thanks for help!
Björn
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992151#3992151
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992151
19 years, 4 months
[JBoss jBPM] - Re: Deleting processInstance as part of workflow
by ksdeger
I think an end-state that would clean up the processInstance would be useful to systems that don't need to keep a history, like ours.
I have figured out some of the answers to my questions (I think). I created a Node with an Action that ends the token, exactly as EndState does. It also calls deleteProcessInstance which is what I wanted. I'm not seeing any bad side affects yet so this solution may work for us.
The only issue I have right now is that not all the entries in the JPBM_BYTEARRAY and JBPM_BYTEBLOCK table are being removed. I believe this may have something to do with the Map being saved multiple times during the process flow, and that somehow ByteArray values are not correctly removed from the database if they are updated. I'm going to keep investigating this issue, as these two tables are causing most of our problems.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992149#3992149
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992149
19 years, 4 months