[Design of JBoss ESB] - Re: Http Gateway - requirements please...
by Kevin.Conner@jboss.com
"dward" wrote : First, why can't ${service.category} be the context?
This is done per esb deployment so there could easily be conflicts with other esb deployments (services in same category) or even other war deployments.
"dward" wrote : Next, can you explain your reasoning why ebws and http paths must be kept separate? The only thing I can think of is if you wanted to provide *both* soap-ws/http and raw-xml/http access to the same service, at which point you'd have to distinguish them somehow.
Someone could choose to do both, for whatever reason, and may even have multiple gateways pointing at the same target service. The EBWS is a fixed, 1-1 relationship but the http need not be. There could easily be different http gateways, with different composers and/or different security constraints, targeting the same ESB service.
"dward" wrote : Last, what if ${service.category} and ${service.name} have spaces in them? The ESB allows for this, but my guess would be that for a url, each space would have to be replaced with %20. Just something to make sure we test.
This is definitely something that we need to test, good point.
Kev
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245048#4245048
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245048
16 years, 8 months
[Design of JBoss jBPM] - Re: Is it possible to avoid hibernate?
by tom.baeyens@jboss.com
"jorgemoralespou_2" wrote : I started by trying to create a new RepositoryService, that hold Deployments in memory (probably a JBossCache in the future). For that I have my MemoryRepositoryService (with its binding in jbpm.user.wire.bindings.xml). I could reuse most of the commands in RepositoryService, but createDeployment has to create a new DeploymentImpl, since the one in the core depends on hibernate (LOB). And from there I have to replicate tons of classes that could have done it if it would have referenced NewDeployment instead of DeploymentImpl.
usually i use protected as the default, so you could consider inheriting the existing services and just overwrite one method with your custom command.
if there is a simple way on how we can make a small change to make your customizations easier, post them very concrete and we'll always consider them.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244930#4244930
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244930
16 years, 8 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Transaction management in JCA adapter is screwed up
by timfox
This is how I think the tx behaviour should be:
1) CMT, tx=NOT_SUPPORTED, local_optimisation = false:
MDB should be *non transacted* - it should use the ack mode as specified in the meta data
2) CMT, tx=NOT_SUPPORTED, local_optimisation = true
MDB should be *non transacted* - it should use the ack mode as specified in the meta data
3) CMT, REQUIRED, local_optimisation = false:
MDB should create a JTA tx *before delivery* and commit at completion of onMessage
4) CMT, REQUIRED, local_optimisation = true
MDB should create a *** local tx *** *before delivery* and commit at completion of onMessage
5) BMT, local_optimisation = false:
MDB should be *non transacted* - it should use the ack mode as specified in the meta data (unless a user transaction is started)
6) BMT, local_optimisation = true
MDB should be *non transacted* - it should use the ack mode as specified in the meta data (unless a user transaction is started)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244925#4244925
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244925
16 years, 8 months