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

[Design of JCA on JBoss] - Re: JCA AOP-MC Integration

by weston.price＠jboss.com

Problems abound :-) It's still the same issue a bean definition such as | <beanfactory name="TraceAdvice" class="org.jboss.resource.aspect.TraceAdvice"/> | | <bean name="TraceAspect" class="org.jboss.aop.microcontainer.beans.Aspect"> | <property name="advice"><inject bean="TraceAdvice"/></property> | <property name="manager"><inject bean="AspectManager"/></property> | </bean> | Fails with: anonymous wrote : | JCABinding | -> TraceAspect{Configured:**ERROR**} | | | *** CONTEXTS IN ERROR: Name -> Error | | TraceAspect -> java.lang.IllegalArgumentException: Wrong arguments. setManager for target org.jboss.aop.microcontainer.beans.Aspect@56f691 expected=[org.jboss.aop.AspectManager] actual=[org.jboss.aop.deployers.AspectManagerJDK5] | Again, this is just a simple test to see if I can get something up and running. The ApectManger that the advice expects is obviously not the AspectManagerJDK5. I looked at the changelog for the prototypes and nothing seemed to change. Can you give me an idea of what you modified? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024762#4024762 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024762

19 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Build System Meeting Agenda Mar 01, 2007

by pgier

"scott.stark(a)jboss.org" wrote : | "pgier" wrote : | | How should we handle thirdparty jars in our repository? One way is to set up a separate repository just for thirdparty artifacts. Another way is to allow developers to add thirdparty stuff to the snapshot repository, and then copy the required files to the release repository when a release is performed. | | | I still need the behavior of snapshot vs non-snapshot described better. We already have 'snapshot' releases in jboss and maven repositories. How does a snapshot repository come into the picture and help things. Layout the pros and cons. | The goal of the snapshot repository is to separate development builds from release builds. Eventually we would like to have only a limited number of people with access to the releases (including alpha, beta, etc) repository. The snapshot repository will be available to all developers and will change much more often. The limitations with the current single repository system are: 1. Release versions of artifacts can be changed by any developer with commit access to the repository. 2. There is not an easy way to clean up old builds. 3. Deploying to the repository requires the extra step of committing, and a time delay before the files appear in the repo. 4. We don't have a way to prevent snapshot versions of dependencies from being included in a release. Having a separate snapshot repository will resolve these issues. We also don't need to have snapshots under version control. I think that maven repositories are not really meant to be under version control. The snapshot builds are basically temporary files, and the release repository should be add only and part of the release process. But it doesn't really hurt to have the releases in cvs or svn. The only drawback I can think of is the extra complexity of having the two separate structures. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024759#4024759 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024759

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Browser-based configuration editor

by derek.adams

I will add an attachment to the JIRA issue with the Flex2 source code for the editor. The tool I used for development was Flex Builder 2 (free-trial, based on Eclipse), but you can download the Flex2 SDK (command-line compiler) for free via a link off this page... http://www.adobe.com/products/flex/. Hope that helps, Derek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024757#4024757 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024757

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Browser-based configuration editor

by kurt.stam＠jboss.com

Just looked at the guide and the code. Very nice. Sorry for my ignorance wrt flash, but what tool do I use to edit the swf file. I'm assuming that's where most of the GUI 'code' lives? Thanks, --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024755#4024755 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024755

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Browser-based configuration editor

by derek.adams

Ok. I posted a JIRA issue for it. Installing it should be as easy as dropping the war in your deploy directory and the action-templates.xml in your conf directory. When the server starts, navigate to http://localhost:8080/esbconfig/ESBConfigEditor.swf and your current config should appear in the editor. I uploaded a PDF user guide as well. Here is the JIRA link http://jira.jboss.com/jira/browse/JBESB-449 that has the files. Let me know what you think! Derek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024750#4024750 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024750

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Browser-based configuration editor

by driedtoast

I second that. That would be nice to have. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024749#4024749 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024749

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Browser-based configuration editor

by kurt.stam＠jboss.com

Thanks looks very nice Derek :). I think it makes a great addition. Please open a jira and it'd be great if you could attach the code there. Thank very much :). --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024742#4024742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024742

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Browser-based configuration editor

by derek.adams

Our company had a requirement to be able to edit the active JBossESB configuration via a web browser interface, so we built a graphical configuration editor. The editor is installed as a war file which contains upload/download servlets for the config and a Flash-based (Flex 2) editor that interacts with them. Here is a screenshot of the interface: [img]http://sourceforge.net/dbimage.php?id=113627[/img] If you guys are interested in making the editor available as an add-on for JBossESB, we would be happy to donate it to the cause. Thanks, Derek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024741#4024741 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024741

19 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Casting to XAConnection in JMSMessageServiceFactoryImpl

by jeffdelong

See this thread on the JMS Dev Forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102050 I notice JMSMessageServiceFactoryImpl looks up JmsXA and casts to XAConnectionFactory I am having problems testing this out right now, but I seem to remember this sort of thing in the past. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024740#4024740 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024740

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Productization of MC 2.0.0

by scott.stark＠jboss.org

A discussion came up today about how to start productizing the MC. One sticking point is the current jbossbuild release which bundles several very different artifacts. We do need to split up the mc project into finer grained consumables to allow more mature pieces to be released and used independent of features driven by jboss5 for example. The break up is described here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024724#4024724 In this thread I want to discuss what pieces we focus on productizing first. Ales believes the core dependency/ioc layers are well defined and should be productized, and that we need to start documenting it. I would agree, and would like to create an overview of the mc architecture as a starting point. This needs to be tied into configuration usecases like the spring, osgi integration, bean deployer, jboss-service rewrite in jboss5, as well as how future notions like scoped kernels fit in. The various mc products needs to be defined and the project dependencies aligned to avoid pulling in things like managed, metatype where we are not ready. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024728#4024728 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024728

19 years, 1 month

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 March 2007