[jboss-user] [JBoss OSGi Users] - OSGi Bundle clustered (farming) deployment ?

2009-10-23 Thread c.vidal
Hi guys and hi Ales, it's been a while :)

I've been kind of away from the JBoss world for some time and digging more into 
the OSGi/Spring world out of frustration from JBoss not clearly embracing OSGi, 
a little more than a year ago.

But recently I stumbled upon JBoss OSGi again and was really pleased to 
discover that JBoss had finally stepped in for good into OSGi. Not only have 
you gotten pretty far into implementing an OSGi container on top of MC but also 
integrating existing third party OSGi containers into JBoss AS which is really 
a smart move. Everyone can now find a suitable match.

What drove me into studying alternative OSGi deployment platforms is the need 
for clustered deployment of bundles. There is Paremus Infiniflow which does 
exactly that and much more but their deployment model is way too complicated 
for the average company. SpringSource DM Server 2 will support it in some way 
but's it's not yet really clear how/when. And both SpringSource DM Server and 
Paremus are not currently on CTO radars whereas JBoss already is.

At the end of the day, I'm looking for a simple way to deploy bundles to a 
cluster of OSGi containers. JBoss farming does exactly that with J2EE 
deployables but will all deployables supported by JBoss MC support distributed 
deployment (farming) ? And more specifically, are/will OSGi bundle farming be 
supported ?

Regarding OSGi, will farming be supported both when JBoss MC is the underlying 
OSGi implementation and when third party OSGi such as Equinox and Felix are 
used ?

Kind regards,

Cédric Vidal
http://blog.proxiad.com


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4261842#4261842

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4261842

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration Deployment] - Re: JBossAS 4.0.5-GA dependency libraries version info relea

2006-12-05 Thread c.vidal
I just saw your answer, thanx a lot for the information, it's very valuable.

Regards,


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3991343#3991343

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3991343
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration Deployment] - JBossAS 4.0.5-GA dependency libraries version info release n

2006-11-22 Thread c.vidal
Hi guys,

could you please point me to a place where I could find a listing of all JBoss 
4.0.5-GA dependencies and especially their versions ?

More generally, this information would be very helpfull for all JBoss releases. 
For most jars, neither the filename nor the MANIFEST indicates version info. 
Most jars have no version info in the filename. I know this is avoided on 
purpose which is fine with me but the problem is that for most jars even their 
MANIFEST version headers are forged.

Sometimes, it is the right original version with an additionnal JBoss 
information:

Manifest-Version: 1.0
  | Specification-Title: Commons Logging
  | Created-By: 1.4.2_09-b05 (Sun Microsystems Inc.)
  | Ant-Version: Apache Ant 1.6.5
  | Implementation-Title: JBoss commons logging patch
  | Specification-Vendor: Apache Software Foundation
  | Specification-Version: 1.0
  | Implementation-Vendor-Id: http://www.jboss.org/
  | Implementation-Version: 1.0.5.GA-jboss
  | Implementation-Vendor: JBoss Inc.
  | Implementation-URL: http://www.jboss.org/
  | 
  | Name: org.apache.commons.logging
  | Specification-Version: 1.0
  | Specification-Vendor: Apache Software Foundation
  | Implementation-Version: 1.0.5.GA-jboss
  | Implementation-Vendor: JBoss Inc.

This is fine with me because you can guess the original version of the 
dependency, here it seems to be commons-logging-1.0.5, but most of the time, 
the version header is equal to the version of the JBoss release which leaves me 
in the dark:

Manifest-Version: 1.0
  | Specification-Title: JBoss
  | JarJarStringTransformer: com.tonicsystems.jarjar.GeneratedStringTransf
  |  ormer
  | Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.)
  | Ant-Version: Apache Ant 1.6.2
  | Implementation-Title: JBoss [Zion]
  | Specification-Vendor: JBoss (http://www.jboss.org/)
  | Specification-Version: 4.0.5.GA
  | Implementation-Vendor-Id: http://www.jboss.org/
  | Implementation-Version: 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610
  |  162339)
  | Implementation-Vendor: JBoss Inc.
  | Implementation-URL: http://www.jboss.org/

The previous MANIFEST was extracted from 4.0.5.GA/server/ejb3/lib/cglib.jar,  
this is absolutely not clear in the MANIFEST.

Thanx for your time,

Regards,

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3987900#3987900

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3987900
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss/Spring Integration] - Re: SpringDeployer compatible with Spring2.0 final

2006-10-19 Thread c.vidal
Hi Ales,

That's great news ! and thanx for the credit :)

Kind regards,

Cédric Vidal

PS: Looking forward to the jndiName attribute removal ;)


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3979503#3979503

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3979503

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss/Spring Integration] - Re: New feature proposal: Add injection interceptor scoped d

2006-10-18 Thread c.vidal
alesj wrote : A single default jndi name isn't ok - since once you deploy 
more that one SpringDeployer app - it would put all BeanFactories under the 
same jndi name - not what we want.
You're right, that's fine with me.

alesj wrote : It should be more deployment specific - something similar to 
EJB3 stuff for persistence context - single persistence context doesn't reqiure 
unit name.
That would be great.

alesj wrote : But working on to it.
Looking forward it ;)

Regards,

Cédric

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3979059#3979059

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3979059

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss/Spring Integration] - Re: New feature proposal: byType injection of Spring beans

2006-09-28 Thread c.vidal
Great, glad to hear that :D


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3974779#3974779

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3974779
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss/Spring Integration] - Re: New feature proposal: byType injection of Spring beans

2006-09-28 Thread c.vidal
Hi Ales,

Here is a quick and dirty patch. I just couldn't wait :) I didn't have the time 
to figure out how the jboss unit tests work though, so I didn't add any unit 
tests. If you could just explain that to me quickly, I'd be glad to add them.

The code tries to do as much guess-work as possible and i'm not sure if it's 
the best way to do it. The algorithm used is explained in the code.

Tell me if it suits you.

Regards,

Cédric


  | Index: 
spring-int/src/main/org/jboss/spring/support/SpringInjectionSupport.java
  | ===
  | --- 
spring-int/src/main/org/jboss/spring/support/SpringInjectionSupport.java
(revision 57255)
  | +++ 
spring-int/src/main/org/jboss/spring/support/SpringInjectionSupport.java
(working copy)
  | @@ -26,6 +26,7 @@
  |  import org.jboss.logging.Logger;
  |  import org.jboss.naming.Util;
  |  import org.springframework.beans.factory.BeanFactory;
  | +import org.springframework.beans.factory.ListableBeanFactory;
  |  import org.springframework.util.Assert;
  |  
  |  import java.lang.reflect.Field;
  | @@ -111,30 +112,101 @@
  |  return m.getName().startsWith(set)  
m.getParameterTypes().length == 1;
  |  }
  |  
  | -private Object getObjectFromBeanFactory(Spring spring) throws Exception
  | +private Object getObjectFromBeanFactory(Spring spring, String 
defaultBeanName, Class type) throws Exception
  |  {
  |  BeanFactory beanFactory = (BeanFactory) 
Util.lookup(spring.jndiName(), BeanFactory.class);
  | -return beanFactory.getBean(spring.bean());
  | +return getObjectFromBeanFactory(spring, beanFactory, 
defaultBeanName, type);
  |  }
  |  
  | +private Object getObjectFromBeanFactory(Spring spring, BeanFactory 
beanFactory, String defaultBeanName, Class type) {
  | +   Object bean = null;
  | +
  | +   if(spring.bean() != null  spring.bean().length()  0) {
  | +
  | +   /*
  | +* If the bean name is specified in the annotation, 
then the bean
  | +* must looked up by name whether the bean factory is 
listable or
  | +* not.
  | +*/
  | +   bean = beanFactory.getBean(spring.bean());
  | +
  | +   } else {
  | +   if (beanFactory instanceof ListableBeanFactory) {
  | +
  | +   /*
  | +* If no bean name is specified in the 
annotation but the bean
  | +* factory is listable then the bean is looked 
up by type.
  | +*/
  | +   ListableBeanFactory listableBeanFactory = 
(ListableBeanFactory) beanFactory;
  | +   Map beans = 
listableBeanFactory.getBeansOfType(type);
  | +
  | +   if(beans.size()  1) {
  | +
  | +   /*
  | +* If there is a ambiguity, try with 
the default name
  | +*/
  | +   bean = beans.get(defaultBeanName);
  | +
  | +   /*
  | +* If no beans amongst the ones of the 
expected type has the
  | +* default name then we can't do 
anything.
  | +*/
  | +   if(bean == null) {
  | +   throw new 
IllegalArgumentException(More than one bean is of type  + type);
  | +   }
  | +
  | +   } else {
  | +   Iterator beansIterator = 
beans.values().iterator();
  | +   if(beansIterator.hasNext()) {
  | +   bean = beansIterator.next();
  | +   }
  | +   }
  | +
  | +   } else {
  | +
  | +   /*
  | +* If no bean name is specified in the 
annotation and the bean
  | +* factory is not listable then the bean can 
only be looked up
  | +* by its default name.
  | +*/
  | +   bean = beanFactory.getBean(defaultBeanName);
  | +
  | +   }
  | +   }
  | +   return bean;
  | +}
  | +
  |  private void injectToMethod(Object target, Method method, Spring 
spring) throws Exception
  |  {
  | -Object bean = getObjectFromBeanFactory(spring);
  | +   String defaultBeanName = getDefaultBeanName(method);
  | +Object bean = getObjectFromBeanFactory(spring, defaultBeanName, 
method.getReturnType());
  |  doAssert(bean, 

[jboss-user] [JBoss/Spring Integration] - Re: New feature proposal: Add injection interceptor scoped d

2006-09-28 Thread c.vidal
Something went wrong with the thread title, it was meant to be called:
anonymous wrote : New feature proposal: Add injection interceptor scoped 
default Spring bean factory JNDI name.


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3974906#3974906

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3974906
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss/Spring Integration] - New feature proposal: Add injection interceptor scoped defau

2006-09-28 Thread c.vidal
Today, you have to specify the spring bean factory's JNDI name in each @Spring 
annotation:
@Spring(jndiName=myApp, bean=SomeBean)
  | private SomeBeanClass pojo;

But most spring based applications use only one bean factory, so it would be 
very convenient as much as less verbose (I'm lazy ;) ) to be able to specify 
the default JNDI name of the bean factory in one place. One such place could 
the SpringInjectionInterceptor. The JNDI name could of course be overriden on a 
per annotation basis. The default JNDI name could be specified in 
ejb3-interceptors-aop.xml the following way:

interceptor class=org.jboss.spring.interceptor.SpringInjectionInterceptor
  | !-- optionnal Spring bean factory default JNDI name --
  | attribute name=defaultJndiNamemyApp/attribute
  | /interceptor
  | 
  | bind pointcut=execution(*-new(..))
  |interceptor-ref 
name=org.jboss.spring.interceptor.SpringInjectionInterceptor/
  | /bind

We then could avoid specifying the jndiName in the annotation:
@Spring(bean=SomeBean)
  | private SomeBeanClass pojo;

What do you think ?

Regards,

Cédric

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3974904#3974904

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3974904

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss/Spring Integration] - New feature proposal: byType injection of Spring beans

2006-09-27 Thread c.vidal
Hi guys,

The current JBoss Spring integration seems to support only byName injection, it 
would be great if it could support also byType injection.

ByType injection of dependencies is a very powerfull feature of Spring, and it 
would be great if it could be leveraged in the JBoss Spring integration. ByType 
injection could be attempted by the SpringInjectionSupport whenever the bean 
attribute of the Spring annotation is missing.

@Spring(jndiName = spring-pojo)
  | private IntCreator intCreator;

This feature is restricted to BeanFactory instances which are 
ListableBeanFactory though. In this case, the method to call is:

Map ListableBeanFactory#getBeansOfType(Class type) throws BeansException;

The only difficulty with this kind of injection is if more than one bean is of 
the expected type. The behavior to follow in that case is described here:
http://static.springframework.org/spring/docs/2.0.x/reference/beans.html#beans-factory-autowire

Is anybody else interested by that functionality ?

Kind regards !


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3974603#3974603

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3974603
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss jBPM] - Re: Custom fork - jbpm 3

2006-07-15 Thread c.vidal
Hi,

I'm also interested by the answer to this :) I'm trying to achieve the exact 
same purpose.

Tchao


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3958271#3958271

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3958271
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user