[Design of JBoss ESB] - Re: Http Gateway - requirements please...
by Kevin.Conner＠jboss.com
It is now time to revisit this work so we need to nail down the requirements. These are the requirements as I see them.
The purpose of this work is to provide a gateway into the ESB using http as the transport mechanism.
We are not writing extensible frameworks to support any transport but, as the current implementation choice is to use a servlet, we should be modifying the current EBWS codebase to share some of the implementation details. We should be deploying a single war file which should have its urls divided into ebws and http sections (perhaps /ebws/* and /http/* or more suitable)
All configuration must be done from within the jboss-esb.xml file, with any deployment artifacts (for example web.xml) being generated solely by the ESB. The HTTP gateway functionality must include the following
- Configurable support for the following verbs: DELETE, HEAD, GET, POST, PUT and automatic support for OPTIONS
- security, covering the following: authentication, transport guarantees, security constraints
- security integrating with Daniel's work
- url patterns
- Configurable synchronous/asynchronous behaviour (mep, timeout, async response)
- No specific servlet integration (e.g. filters/listeners)
There will probably be areas of this that needs to be fleshed out further, but this should provide the integration we need without exposing the specific details of the implementation.
Kev
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244908#4244908
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244908
17 years
[Design of JBoss jBPM] - Re: Whether the JBPM4.0 support informix
by superjoo
Oh,my god!I'm so sorry.
| <session-factory>
|
| <property name="hibernate.dialect">
| org.hibernate.dialect.InformixDialect
| </property>
| <property name="hibernate.connection.driver_class">
| com.informix.jdbc.IfxDriver
| </property>
| <property name="hibernate.connection.url">
| jdbc:informix-sqli://192.251.1.150:1528/xjtcyy:informixserver=vseal
| </property>
| <property name="hibernate.connection.username">xwj</property>
| <property name="hibernate.connection.password">xwj123</property>
| <property name="hibernate.hbm2ddl.auto">create-drop</property>
| <property name="hibernate.format_sql">true</property>
| <property name="myeclipse.connection.profile">informix</property>
| <property name="connection.url">jdbc:informix-sqli://192.251.1.150:1528/xjtcyy:informixserver=vseal</property>
| <property name="connection.username">xwj</property>
| <property name="connection.password">xwj123</property>
| <property name="connection.driver_class">com.informix.jdbc.IfxDriver</property>
| <property name="dialect">org.hibernate.dialect.InformixDialect</property>
|
| <mapping resource="jbpm.repository.hbm.xml" />
| <mapping resource="jbpm.execution.hbm.xml" />
| <mapping resource="jbpm.history.hbm.xml" />
| <mapping resource="jbpm.task.hbm.xml" />
| <mapping resource="jbpm.jpdl.hbm.xml" />
| <mapping resource="jbpm.identity.hbm.xml" />
|
| </session-factory>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244898#4244898
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244898
17 years
[Design of JBoss jBPM] - Re: Is it possible to avoid hibernate?
by kukeltje
anonymous wrote : Is jBPM targeted to be extendible by developers from outside JBoss.org?Yes it is, but for now that is limited to make custom nodes, eventhandlers etc.. and to some extend custom services (like IDM).
As mentioned earlier by Tom (second post)
anonymous wrote : that is a target. but we'll be only able to bring this to the surface in the mid term
and the fourth post:
anonymous wrote : the direction we're thinking in for that use case is to use the ProcessBuilder to create process definitions. Probably we can leverage the JpdlParser for that as wel. That will immediately give most of jPDL features instead of having to start from an empty PVM. Maybe some dependencies on the environment configuration sneeked in here or there.
|
| Our current idea is to use methods on the objects themselves for the memory execution mode, and skip the services api's
|
| It would be great if you could try that direction and see where you run into problems.
So yes it is, but you are 'early' and doing groundbraking work :-).
anonymous wrote : If so, I think that one really lacking feature is design documentation, as I have to dive into the internal API, where there is no much javadoc, nor documentation.
And yes, that is one of the reasons docs in this area are not there.
anonymous wrote : I'll try to post my questions in here as they arise in the hope of letting me fulfill my requirements, and I'll try to flood the list with requests and questions, so In Memory Process Execution can become a reality.
What you do is of interest, and with detailed questions in separate topics I'm sure the core devs are willing to help/comment.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244876#4244876
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244876
17 years