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

[Design of JBoss Labs] - Blog Portlet does not use Seam

by jboss＠biancashouse.com

I got very excited when I read that Blog had now been made into a proper portlet. Great, I thought, now there's a real example of how to use Seam and facelets in a portlet. On inspecting the sar, I find that Seam is not used. Are you planning to migrate this portlet code to use Seam in the future ? The only reason I ask is that I'm waiting for someone to produce an example that finally will figure out all the xml hell that is required to get a Seam portlet up and running. Thanks, Ian Sydney View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013927#4013927 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013927

19 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - GPD New Generation Extensibility

by koen.aers＠jboss.com

anonymous wrote : Hi Koen, | | Am trying to do it on my own - am running into an issue with the JpdlLabelProvider. The list of icons and labels is hard-coded in here - are you planning to expose these via additional elements/attributes on the "core" and "ui" element extensions? | | thanks, | Mohan | Hi Mohan, Nice to see that you are investigating the GPD code. Please don't hesitate to use this forum to ask questions and generate feedback if you think things can be improved. As for your question, the new generation of the GPD is not yet ready for custom extensions. As you correctly have observed, not all the necessary information can be specified in the available extension points. In some places (such as the label provider and the editpart factories) big switch/case logic is present to select the right icon or figure. Also the editpolicies can not yet be specified in the plugin.xml. Well, to be more correct, the extensions are not used at the moment. These capabilities (custom extensions of the GPD) will certainly *not* make it into the 3.1.0 GA release because of time constraints. They will be however most certainly be part of a future release in the 3.1.x branch. I know the answer is probably disappointing. However, if you really want to do a custom extension right now, you can identify the places where the switch/cases are found, and replace those classes with your own implementation. Best regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013870#4013870 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013870

19 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Legacy (1.0.x) jboss common maven2 repo location

by scott.stark＠jboss.org

19 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - jboss-vfs.jar version 1.0.x for jbossas 4.2.x

by scott.stark＠jboss.org

I took a look at creating a jboss-vfs.jar version for 4.2 that is based off of the 1.0.x jboss-common.jar. This can be done. The only thing missing from the current 1.0.3.GA jboss-common.jar are changes to the org.jboss.util.file.ArchiveBrowser. These can be backported to jboss-common for a 1.0.4.GA release. I'm going to create a Branch_1_0 under https://svn.jboss.org/repos/jbossas/projects/vfs/branches for this. This can be integrated as a server/xxx/lib jar rather than a bootstrap jar I believe. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013793#4013793 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013793

19 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: VirtualFile abstraction

by scott.stark＠jboss.org

I took a look at just creating a jboss-vfs.jar version for 4.2 that is based off of a jboss-common.jar. This can be done. The only thing missing from the current 1.0.3.GA jboss-common.jar are changes to the org.jboss.util.file.ArchiveBrowser. These can be backported to jboss-common for a 1.0.4.GA release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013790#4013790 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013790

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by alesj

"alesj" wrote : | "adrian(a)jboss.org" wrote : | | | | | <deployment scoped="false"> | | | | | | I would also like to support separate deployments - no parent Kernel(Controller). Code tag slipped by. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013776#4013776 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013776

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by alesj

"adrian(a)jboss.org" wrote : | The bindings are done against the MutableMetaData which is a shared | repository. It already has a notion of scope. | What's the usage of the bindings if we have the underlying architecture - with whole deployment already being deployed in scope. "adrian(a)jboss.org" wrote : | In both cases, you pick out all the "scope" annotations. | How do I tell them apart - via @ScopeFactoryLookup? "adrian(a)jboss.org" wrote : | | I would also like to support separate deployments - no parent Kernel(Controller). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013775#4013775 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013775

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : | | So this means that Bindings should be deployed against new (Scoped)Kernel, not against the underlying. | | The bindings are done against the MutableMetaData which is a shared | repository. It already has a notion of scope. | | The scoped kernel is a different feature. | That is where you would do something like: | | | | <deployment> | | <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope</annotation> | | </deployment> | | | | This would: | | Stages (1) and (2) are optional if they already exist | | 1) Create a MutableMetaData for this scope | 2) Create a kernel (or maybe just a kernel controller) for this scope and add it to | the MutableMetaData, the kernel's parent would come from any kernel in the | parent's scope or the default kernel if there is no such thing | 3) Deploy the bean(s) into that scoped kernel | | You should also support things like: | | | <deployment> | | <bean> | | <annotation>@org.jboss.metadata.plugins.scope.SubsystemScope("jca")</annotation> | | </bean> | | </deployment> | | | | In both cases, you pick out all the "scope" annotations. | | Iincluding those that are on the bean class if they are not overridden. | The MetaData (read only context) already has the processing to do this | since each instance scope has a parent scope of the class. | | For ease of use (less boiler plate) I've also previously suggested or would suggest: | | 1) The qualifier for @org.jboss.metadata.plugins.scope.DeploymentScope | should come from KernelDeployment.getName() if the user doesn't specify it. | 2) Support simple scoping definitions directly in the xml, e.g. | | | <deployment scoped="true"> | | | The latter being the same as just adding the DeploymentScope annotation | to the deployment. | | NOTE: We don't have any processing at the moment that lets you add | annotations at the deployment level. This is obviously a useful feature | where you want all beans to have the same annotations, like the scope. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013761#4013761 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013761

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

"alesj" wrote : | You probably meant this code: | | | ScopeKey scope = from the <scope/>; | | You need to combine all the scopes. In fact, the stuff we talked about before is probably better as a Scope rather than a ScopeKey. You would then create the ScopeKey from all the scopes | /** | * Create a new ScopeKey. | * | * @param scopes the scopes | */ | public ScopeKey(Collection<Scope> scopes) | { | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013747#4013747 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013747

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by alesj

"adrian(a)jboss.org" wrote : | The policy xml should be unmarshalled to an object that implements | BeanMetaDataFactory. When the deployment invokes getBeans() | that object will create some BeanMetaData for a POJO | that knows how to install/uninstall data into the MetaData repository. | | | | public class MetaDataRepositoryInstaller | | { | | public void setScope(ScopeMetaData); | | | | @Inject // If we can assume there be will only one instance? | | public void setKernelMetaDataRepository(KernelMetaDataRepository) | | | | // The MC will resolve the ValueMetaData to objects! | | public void setMappings(Map<String, Object>) | | | | public void start() | | { | | // Install | | } | | | | public void stop() | | { | | // Uninstall | | } | | } | | | You probably meant this code: | // Get a link to the scoped metadata | KernelMetaDataRepository kmdr = kernel.getMetaDataRepository(); | MutableMetaDataRepository mmdr = kmdr.getMutableMetaDataRepository(); | ScopeKey scope = from the <scope/>; | MutableMetaData mmd = (MutableMetaData) mmdr.getMetaDataRetrieval(scope); | | // Not found create it | if (mmd != null) | { | mmd = ...; | mmdr.addMetaDataRetrieval(mmd); | } | | for (iterate) | mmd.addMetaData(name, object, object.getClass()); | into MetaDataRepositoryInstaller.start()? So this means that Bindings should be deployed against new (Scoped)Kernel, not against the underlying. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013741#4013741 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013741

19 years, 2 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 February 2007