July 2009 - jboss-dev-forums - Jboss List Archives

[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

1
0
0 / 0

[Design of JBoss ESB] - Re: Http Gateway - requirements please...

by dward

First, why can't ${service.category} be the context? Are we worried about "too many wars" being deployed? 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. 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. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245043#4245043 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245043

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Moving Messages Twice and LargeMessage links

by timfox

Ok I understand what you mean now. I think that would be ok. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245025#4245025 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245025

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Moving Messages Twice and LargeMessage links

by clebert.suconic＠jboss.com

I' m just using the property _JBM_ORIG_MESSAGE_ID to refer to the original message. I' m adding a linked message property on LargeMessage, and I' m keeping a reference count on the linkedMessage. When the message reference count is 0, I just remove a reference counting from the linked message. With the current implementation I have a problem when the message is moved for the second time, as the property won't reference to the original message any more. Because of that, if a message is moved again, I' m referring to the first original messageID. I just wanted to know if this would be ok or not? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245021#4245021 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245021

16 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Http Gateway - requirements please...

by Kevin.Conner＠jboss.com

"dward" wrote : I'm not a big fan of those url patterns. I would rather see: | http://host/${service.category}/${service.name} Well this can certainly be the default although the endpoint must be something like http://host/context/http/${service.category}/${service.name} There must be a way to separate ebws from http. We already have a context because of the war and we need to further divide that into two areas, there must be a way to separate ebws from http. "dward" wrote : web services specifically (whether they be ebws, the new webservice proxy stuff, ...), I would want the wsdl to be available there also per "?wsdl" convention: | http://host/${service.category}/${service.name}?wsdl This should already be handled for EBWS because of the JBossWS integration. As for the rest, can we please get the http gateway working first before we go off track and implement other features? Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245017#4245017 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245017

16 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Http Gateway - requirements please...

by dward

"Kevin.Conner(a)jboss.com" wrote : 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) | I'm not a big fan of those url patterns. I would rather see: http://host/${service.category}/${service.name} , and for web services specifically (whether they be ebws, the new webservice proxy stuff, ...), I would want the wsdl to be available there also per "?wsdl" convention: http://host/${service.category}/${service.name}?wsdl This would be in addition to the contract wsdl urls we have now. In fact, a brainstorm way for the "?wsdl" to easily work would be for there to be a servlet filter in the new http gateway that catches anything that ends in "*?wsdl" and request dispatches over to the existing contract wsdl location, which can be inferred by parsing the request uri path for /${service.category}/${service.name}. Thoughts? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245006#4245006 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245006

16 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Whether the JBPM4.0 support informix

by superjoo

Thanks for your help.Few days ago,I used JBPM 3.2.6 and informix 9.4 to deploy my application.I made 30 Processes start the ProcessInstance at the same time,Then the aplication throw database Deadlock Exceptions.Then I asked the informix technology support,he told me that some sessions operated the JBPM_TOKEN table at the same time and two sessions made the Deadlock error.So I use 4.0version to test whether there are same questions between JBPM3.0 and informix.It's a pity that I'm not success.I'll try again later and thank you again. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244961#4244961 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244961

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - PagingManager activation

by timfox

Quick question: Why does a pagingmanager on activation start a global depage? Why doesn't it start depaging each address individually as on the live? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244931#4244931 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244931

16 years, 8 months

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2009