Related to JBAS-6242, a general problem for the jon usage of managed objects is that they need more information about operation return types when they are opaque types like Object mapping to anything from a GenericValue to a String. For operations that do have a fixed type the return type should be mapped to that.
For operations that can change based on other settings as is the case for the JBAS-6242, I guess we have to impose a fixed type that a MetaMapper will have to handle producing based on the possible return types.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236776#4236776
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236776
Nothing changed on this regard.
Writes are aways sent on executors.. (On AIO, the main thread never block on a write, unless it is waiting for a sync callback).
There is aways a file opened, and another file is immediately created when that file is returned.
Perhaps, the only thing that changed was... we can get better throughput on the disk. If your disk is maxed out (your laptop for instance) the file creation may be competing with the journal write process. If the disk throughput is maxed out, the time to create a new file may be higher than the ammount of time needed to fill up a file, on that case we will have eventual pauses waiting for new files to be opened.
I aways have seen this happening before.. and I've done a lot of testing around this.
But I will take a look, see if we can improve anything on the process of files-creation.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236754#4236754
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236754
I agree, the initialContext should be cached
I thought the discussion of ejb2 vs ejb3 was done in the past and I think that tom wanted to have support on as many application servers as possible. Altough I must agree that I like EJB3 much much more ;)
anonymous wrote : In combination with the command interface in jBPM 3.0 not being really supported/documented and thus probably not being used much
Everywhere I've done jbpm consultancy, they are using the CommandService ;-)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236753#4236753
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236753