[Design of JBoss jBPM] - Re: extending form / task functionality
by tom.baeyens@jboss.com
i think i initially created a separate forms.xml to avoid that the task definition gets an extra column in the database.
but now i don't think this is important. so we probably will go to moving the task form reference to the task in the processdefinition.xml.
this will impact the designer so we will have to carefully coordinate such a change. koen, how hard would this be for you (the update and verifying if/how this could break compatibility) ?
xhtml files in the webapp i think is already possible but i'm not sure. David, do you know that ?
i think it could be possible to support both xhtml and jsp files. the taskForm field of the task could become something like this: The webapp could look at the extension and based on that redirect to a separate jsp or include the xhtml into a template form page as is done now.
let me know where this doesn't make sense cause i had to write this fast because koen is waiting for me to get a sandwish :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979615#3979615
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979615
19 years, 5 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remoting - Multiplexed (Bidirectional) Transport
by timfox
"ovidiu.feodorov(a)jboss.com" wrote :
| From an API perspective, client to server invocations (synchronous and asynchronous) and server to client callback (synchronous and asynchronous) is all we need. Remoting is very close to that, and I will soon publish a wiki document with suggested API amendments. But this is not the problem. The problem is that we don't need to mess around with virtual sockets to get bi-directionality. A TCP connection is inherently bi-directional. You write stuff at this end and it comes out at the other end. You write stuff at the other end and it comes out at this end. Remoting should take advantage of that in the simplest way possible. Write a different transport for that, call it "bidirectional" or "nebuchadnezzar", doesn't matter, and Messaging will use it.
|
+1.
A bidirectional transport core abstraction is what I have been suggesting from the beginning.
It just make more sense, and prevent us having to jump though fiery hoops (callback servers, virtual sockets) to get a simple(ish) job done.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979595#3979595
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979595
19 years, 5 months