April 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Web Services] - Compatibility between WS and later versions of remoting

by timfox

Hello web services people :) We are having a debate over on the messaging design forum http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037674#4037674 about patching JBAS 4.x to allow us to deploy jboss messaging unscoped in it. Apparently there is an issue with doing this and web services - something to do with compatibility between the version of WS in earlier versions of 4.x and later versions or JBoss Remoting. Can any of you guys remember what this issue is? Would it require us to produce a patched version of JBWS and install it when we deploy JBM in 4.x? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037677#4037677 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037677

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Patching app server versus scoping messaging

by ovidiu.feodorov＠jboss.com

"timfox" wrote : | In which case I would prefer dropping scoping altogether - one less piece of complexity to maintain/support. Come on, scoping has so many elegant theoretical implications! :) Why getting rid of it? :) Of course, I agree with you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037676#4037676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037676

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Patching app server versus scoping messaging

by timfox

"ovidiu.feodorov(a)jboss.com" wrote : | My suggestion would be to change release-admin.xml (or the graphic installer, if there is one) to offer the choice of going scoped (solid, but PITA), or unscoped (hacky, but easy to use and actually solid as well) I suppose if we can make sure that everything (web services etc) works ok using the patching method, then this is just as "solid" as deploying scoped. In which case I would prefer dropping scoping altogether - one less piece of complexity to maintain/support. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037674#4037674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037674

18 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Upgrade to Hibernate 3.2.3

by alex.guizar＠jboss.com

JBoss AS 4.2 is going to include Hibernate 3.2.3.GA. We are currently at 3.2.1.GA. As a preventive move, I am about to update our build.properties. Let me know if this affects you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037665#4037665 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037665

18 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: update and remove methods in the process definition clas

by alex.guizar＠jboss.com

If I recall correctly, these methods were created back when the GPD manipulated the definition classes directly. After a while it became apparent that manipulating the definition classes directly was not practical. The only use case I can think of is to modify the definition after deployment. However, this requires much more than update and remove methods. IMO we should deprecate them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037662#4037662 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037662

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Patching app server versus scoping messaging

by ovidiu.feodorov＠jboss.com

* Overwrite jboss-remoting.jar with whatever comes with our release * Modify our jboss-service.xml to make it unscoped * Replace significant ejb3 jars. Carlos has a patch procedure, and so Robb Greathouse, who applied it. I'll ping both of them, so they can comment on the thread. This part is a little hazy at this moment, we need to address it carefully. Overwriting aop dependencies is part of this procedure, as far as I remember, but messaging works fine with * Web Services won't work, afaik, so we need to coordinate with them. I don't know specifics, I just deleted their artifact from the deployment directory. * We need to modify our smoke test procedure to check this new configuration. If you can wait until the end of the week, I can give it a try (create a JIRA issue and assign it to me, so I can manage this easily) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037658#4037658 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037658

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Patching app server versus scoping messaging

by timfox

Hi Ovidiu- Ok so we would have to do: Overwrite jboss-remoting.jar in server/lib with the latest one Overwrite the ejb3 jars in server/lib with the ones patched already Carlos (I wonder if the patch is in a GA of EJB3 yet?) Overwrite jboss-aop.jar with the latest one. You say web services will be a problem - do you have any more details? Would we need to patch web services, or patch remoting? Cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037656#4037656 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037656

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Patching app server versus scoping messaging

by ovidiu.feodorov＠jboss.com

I know big shops that already did this and everything works fine. However, EJB3 needs patching for this, Carlos already has the patch. WebServices are a problem, though, your configuration won't support the latest ws releases, unless patched. My suggestion would be to change release-admin.xml (or the graphic installer, if there is one) to offer the choice of going scoped (solid, but PITA), or unscoped (hacky, but easy to use and actually solid as well) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037644#4037644 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037644

18 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Finding the EPR for a provider from a notifier

by mark.little＠jboss.com

"derek.adams" wrote : Deployment of the actual providers that implement functionality for the EPRs is something I have been wondering about too. | You mean the service implementations, right? anonymous wrote : Right now, the providers for file, FTP, JMS, etc are tightly coupled to the framework itself. | OK, maybe you don't ;-) Can you explain? anonymous wrote : It seems like the providers should be deployed separately in their own SARs, and hot-deployed by the ESB. The SAR would include all of the implementation code and some kind of descriptor that contains a list of the EPRs available from the provider. Each EPR listed would have a unique identifier so that it could be referenced from the -esb.xml to create an EPR instance (would require using the generic schema elements rather than the provider-specific ones). | This is slightly confusing, but then that could be because I don't get the "provider" definition. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037640#4037640 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037640

18 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Finding the EPR for a provider from a notifier

by mark.little＠jboss.com

"kurt.stam(a)jboss.com" wrote : However when I get that scout bug fixed we could start adding a second class of EPRs which represent non-ESB-aware endpoints. Question is, who is going to add these EPRs to the registry. The thirdparty systems that represent these non ESB aware endpoints won't "autoregister" like the ESB aware services do. | Although an EPR can represent anything (including a vanilla URL), not everything need be represented as an EPR outside of the ESB domain. There are pros and cons to this, of course. But it's worth adding to the discussion "pot". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037638#4037638 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037638

18 years, 11 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 April 2007