[Design of Clustering on JBoss (Clusters/JBoss)] - Using JBossSerialization with HttpSession Replication (JBAS-
by hmesha
Hi all,
discussion for JBAS-2921
Currenlty, Http Session replication employ JavaSerialization to perfrom object serialization before inserting sessions or attributes in the cache. What we would like to do is provide an additional option to use JBossSerialization. The problem there's no server wide configuration property to toggle between JavaSerialization and JBossSerialization.
Here's the solution that I'm proposing
1. provide a configurable property in jboss-web.xml. Possible values are:
<session-serialization>JBossSerialization</session-serialization>
or
<session-serialization>JavaSerialization</session-serialization> (default value)
or
<NOT EXIST> (default to JavaSerialization)
2. add dependency on JBossRemoting to take advantage of SerializationStreamFactoryMBean where we set and get the serialization manager from the factory.
3. Based on the serialization type specified in step 1 we can invoke the either JBossSerializationManager or JavaSerializationManager (default) to create the needed MarshalledValue to serialize the objects
Thoughts?
-Hany
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967904#3967904
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967904
18 years
[Design of JBoss jBPM] - Re: web services question
by kukeltje
AAAHHHHHHHHHHH sorry, forgot to do a final preview
ahh ok, The initial trials were handcoded. The best/easiest/standardized (in no order of preference) way of mapping is what I'm looking into. It could be that they can map easisly on commands, but then they have to be aligned. There are 2 options I'm investigating:
| <command name="startProcess">
| <processDefinition>
| <name>procName</name>
| <version>1.0</version>
| </processDefinition>
| <variables>
| <variable>
| <name>damageDate</name>
| <value>090906</value>
| </variable>
| <variable>
| <name>amount</name>
| <value>191916</value>
| </variable>
| </variables>
| </command>
|
Personally I'm more in favour of:
| <startProcess>
| <processDefinition>
| <name>procName</name>
| <version>1.0</version>
| </processDefinition>
| <variables>
| <variable>
| <name>damageDate</name>
| <value>090906</value>
| </variable>
| <variable>
| <name>amount</name>
| <value>191916</value>
| </variable>
| </variables>
| </startProcess>
|
But this is not so extensible... If we make all elements optional, adding custom commands will be easier in XML, but they still have to be mapped. to either methods that did not exist or add some kind of config to fiond these base on reflection or whatever. Extending commands should benefit all and just be in the code. So I'm looking into the latter solution. I want to generate and XSD first with the commands in mind, but if some coding needs to be done, so be it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967894#3967894
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967894
18 years
[Design of JBoss jBPM] - Re: transactions, commands and packaging
by david.lloyd@jboss.com
The way I see it, no transaction should span more than a single request or form submission on the webapp. In read/modify/write cases we should (if we have not already) adopt an optimistic locking style of strategy, where we trigger an error on form submit if the relevant server state has changed between the request of the form and the submission of the same form.
That said, I don't see why we can do whatever we want with transations, at least with respect to the web application.
My apologies if I'm duplicating what you've already said.
Also, I don't really like the idea of keeping a heavyweight state on the web application side either. Ideally the web application would be purely stateless. Of course this may or may not be possible - I'm still not familiar enough with the API to know for sure. Working on it though!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967872#3967872
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967872
18 years