jboss-dev-forums

[Jboss-dev-forums] [Design of JBoss Web Services] - Re: JBoss integration redesign

[<sco...@jb...>]

This is a mc/jmx kernel bridge issue that we should have better support for or else the beans deployer really does not integrate into the jboss-4.0.x release. What you need is an ability to import the foreign jmx kernel service into the mc as a bean for dependency purposes. 

With what your proposing, aren't you going to be duplicating a kernel and therefore breaking another mc bean deployment from interacting with the jbossws beans?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953593#3953593

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953593

[Jboss-dev-forums] [Design of JBoss Web Services] - Re: JBoss integration redesign

[<jas...@jb...>]

"sco...@jb..." wrote : This is a mc/jmx kernel bridge issue that we should have better support for or else the beans deployer really does not integrate into the jboss-4.0.x release. What you need is an ability to import the foreign jmx kernel service into the mc as a bean for dependency purposes. 
  | 

Yes, that would definately solve the problem.


anonymous wrote : 
  | With what your proposing, aren't you going to be duplicating a kernel and therefore breaking another mc bean deployment from interacting with the jbossws beans?
  | 

Yes, although this is what the current mc deployer does. It creates a new kernel per deployment.

-Jason

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953727#3953727

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953727

[Jboss-dev-forums] [Design of JBoss Web Services] - Re: JBoss integration redesign

[<sco...@jb...>]

"jas...@jb..." wrote : 
  | Yes, although this is what the current mc deployer does. It creates a new kernel per deployment.
  | 

Ok, I did not realize that. Then I guess its just a question of is it worth the extra time to add support for integration of dependencies on jmx kernel beans to the deployer vs essentially creating a custom bean deployer for the jbossws usecase. The former is what I would prefer. I'll post in the mc forum on what it would take to get this done. Lack of followup would a green light to do what you want.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953785#3953785

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953785

[Jboss-dev-forums] [Design of JBoss Web Services] - Re: JBoss integration redesign

[<sco...@jb...>]

The MC thread:
[http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953787[/url]


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953788#3953788

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953788

[Jboss-dev-forums] [Design of JBoss Web Services] - Re: JBoss integration redesign

[<jas...@jb...>]

"sco...@jb..." wrote : 
  | Ok, I did not realize that. Then I guess its just a question of is it worth the extra time to add support for integration of dependencies on jmx kernel beans to the deployer vs essentially creating a custom bean deployer for the jbossws usecase. The former is what I would prefer. I'll post in the mc forum on what it would take to get this done. Lack of followup would a green light to do what you want.

I agree, the former is ideal because this is a problem that will affect other projects as they migrate to the mc. I will monitor the thread.

-Jason



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953794#3953794

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953794

[Jboss-dev-forums] [Design of JBoss Web Services] - Re: JBoss integration redesign

[<tho...@jb...>]

Jason, 

I suggest we stay away from a fix in the jbossws codebase. As we all agree, this should be solved in a general way for all MC beans with dependencies on jboss services.

For the next release, we disable the eventing subsription manager by default and document that it can only be enabled when the JNDI service is part of conf/jboss-service.xml

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953952#3953952

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953952

[Jboss-dev-forums] [Design of JBoss Web Services] - Re: JBoss integration redesign

[<hei...@jb...>]

I agree with thomas. Especially since our deployment problem doesn't exists anymore. I managed to tweak the eventing parts to lazily access the naming service. That means we can take our time and start looking at the mc2jmx bridge scott suggested.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954265#3954265

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954265

[Jboss-dev-forums] [Design of JBoss Web Services] - Re: JBoss integration redesign

[<jas...@jb...>]

An MC task was just created by scott to do this, so I have added a corresponding task on our side to make use of it.

http://jira.jboss.com/jira/browse/JBWS-1030

-Jason


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954584#3954584

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954584