May 2010 - jboss-dev-forums - Jboss List Archives

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Brad Davis

Brad Davis [http://community.jboss.org/people/bradsdavis] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541596#541596 -------------------------------------------------------------- See: What were those reasons? Did you consider at the time that if 10 services use the deployment descriptor to depend on the Proxy service which fails, all 10 of those dependant services will also fail? And then any services that rely on those 10 services could also then fail? That is what I mean by domino affect. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541596#541596] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Kevin Conner

Kevin Conner [http://community.jboss.org/people/Kevin.Conner%40jboss.com] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541595#541595 -------------------------------------------------------------- > localhost is really irrelevant; It is irrelevant because it tells you nothing, you cannot base any decision on it. Kev -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541595#541595] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by David Ward

David Ward [http://community.jboss.org/people/dward] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541594#541594 -------------------------------------------------------------- > Brad Davis wrote: > > > Yes, this is deliberate at present because we publish the derived WSDL and validate the configuration at that point. As mentioned earlier in the week though, this is easy to work around by using a local copy of the WSDL and will give you the behaviour you require. > > I am saying if this is deliberate, we should fix it because it is a design flaw. That is why I opened the support ticket. I'm sorry, I can't resist responding. How is this a design flaw? If we went with a lazy approach, then we would have a deployed service for which we would +not+ be able to expose WSDL for! We need to pull in the WSDL on initialization so we can transform it and provide it to consumers of the ESB. If we went the lazy way, we would get +more+ bug reports from people saying "WSDL contract unavailable!" -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541594#541594] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Brad Davis

Brad Davis [http://community.jboss.org/people/bradsdavis] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541593#541593 -------------------------------------------------------------- What were those reasons? Did you consider at the time that if 10 services use the deployment descriptor to depend on the Proxy service which fails, all 10 of those dependant services will also fail? And then any services that rely on those 10 services could also then fail? That is what I mean by domino affect. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541593#541593] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Brad Davis

Brad Davis [http://community.jboss.org/people/bradsdavis] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541592#541592 -------------------------------------------------------------- > Sorry, localhost is an IP address and is not relevant. It is the referrral of a service within the same VM that can cause it to hang if goes through the web server valve. Precisely my point. localhost is really irrelevant; the point is, the SoapProxy should not freeze a deployment, no matter if the service lies on the same server or a different server. And additionally, it should be tolerant when the proxied service is up or down. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541592#541592] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Kevin Conner

Kevin Conner [http://community.jboss.org/people/Kevin.Conner%40jboss.com] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541591#541591 -------------------------------------------------------------- > I am saying if this is deliberate, we should fix it because it is a design flaw. And I have been saying that we are doing it deliberately for good reasons. It was not a decision that was taken lightly. Kev -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541591#541591] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Brad Davis

Brad Davis [http://community.jboss.org/people/bradsdavis] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541590#541590 -------------------------------------------------------------- > If you chose to use a different SOAP stack, perhaps as a servlet within one of your deployments, then it would not help. I don't think in an ESB we should be restricting people to use one SOAP stack. Especially considering some people prefer the Spring + CXF stack. Or have legacy endpoints written in Axis. The whole point of an ESB is to integrate with many technologies. Considering legacy apps is one of the main drivers in ESB integrations in the field, it is not a viable solution to say "our ESB only works with JBossWS!" -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541590#541590] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Kevin Conner

Kevin Conner [http://community.jboss.org/people/Kevin.Conner%40jboss.com] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541589#541589 -------------------------------------------------------------- > if localhost:// causes a server freeze Sorry, localhost is an IP address and is not relevant. It is the referrral of a service within the same VM that can cause it to hang if goes through the web server valve. Kev -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541589#541589] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Brad Davis

Brad Davis [http://community.jboss.org/people/bradsdavis] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541588#541588 -------------------------------------------------------------- > Yes, this is deliberate at present because we publish the derived WSDL and validate the configuration at that point. As mentioned earlier in the week though, this is easy to work around by using a local copy of the WSDL and will give you the behaviour you require. I am saying if this is deliberate, we should fix it because it is a design flaw. That is why I opened the support ticket. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541588#541588] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - SOAPProxy initialization and deployment ordering

by Kevin Conner

Kevin Conner [http://community.jboss.org/people/Kevin.Conner%40jboss.com] replied to the discussion "SOAPProxy initialization and deployment ordering" To view the discussion, visit: http://community.jboss.org/message/541587#541587 -------------------------------------------------------------- > The documentation says that internal:// is reserved for JBossWS. Correct, it can only be used against JBossWS services running within the same VM as it uses a JBossWS internal API. If you chose to use a different SOAP stack, perhaps as a servlet within one of your deployments, then it would not help. Kev -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541587#541587] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2010