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

Re: [jboss-dev-forums] [JBoss XML Binding Development] - JBJPA-27 and setting PersistenceUnitMetaData reference to PersistenceMetaData

by Scott Marlow

Scott Marlow [http://community.jboss.org/people/smarlow%40redhat.com] replied to the discussion "JBJPA-27 and setting PersistenceUnitMetaData reference to PersistenceMetaData" To view the discussion, visit: http://community.jboss.org/message/540464#540464 -------------------------------------------------------------- Is there any reason why CollectionPropertyHandler.handle(PropertyInfopropertyInfo, TypeInfo propertyType, Object parent, Object child, QName qName) couldn't call the the getter after setting the field? It appears that we call the getter before the set, but not after. It is no good to wait until the application calls the getter (since the application may first call PUMD.getPMD() which would return null. If the convention is to put initialization logic in the getter, perhaps XB should call the getter after setting the field. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540464#540464] Start a new discussion in JBoss XML Binding Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - JBPM-2537

by Sebastian Schneider

Sebastian Schneider [http://community.jboss.org/people/sebastian.s] replied to the discussion "JBPM-2537" To view the discussion, visit: http://community.jboss.org/message/540455#540455 -------------------------------------------------------------- Huisheng Xu: I was not aware of this issue and its bugfix. Thank you for pointing out. Nevertheless I don't see why adding this method to ExternalActivityBehaviour is not a good design. Ronald has been thinking this carefully. When implementating custom nodes which also need a timeout behaviour this would be already useful. Please also consider Maciej's point: For me cancelling a task and timeouts have to be clearly distinguished from the completion and deletion of tasks because they all mean different history data being related. If there is an escalation/timeout I don't want the task to be treated as if it was deleted. Deleting tasks should only be possible for tasks not belonging to a process/execution. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540455#540455] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Microcontainer Development] - JBREFLECT-5 - Implementing generics in JavassistClassInfo

by Kabir Khan

Kabir Khan [http://community.jboss.org/people/kabir.khan%40jboss.com] replied to the discussion "JBREFLECT-5 - Implementing generics in JavassistClassInfo" To view the discussion, visit: http://community.jboss.org/message/540441#540441 -------------------------------------------------------------- > Kabir Khan wrote: > > Removing the cache for parameterized types largely works, although I need to fix some StackOverflowErrors when using recursive bound type variables such as > > *public* *class* ClassInfoTypeVariableRecursiveBounded<T *extends* ClassInfoTypeVariableRecursiveBounded<T>> > { > *public* T genericTypeVariableRecursiveBounded(T param, String s) > { > *return* *null*; > } > > } > This has been fixed. I needed to add this method to ClassInfo /** * Gets the type variable if we are a parameterized type which is part of a * parameterized type and there is a type variable for this type. This is * useful in avoiding infinite recursion * * @return the type variable */ String getTypeVariable(); -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540441#540441] Start a new discussion in JBoss Microcontainer Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Microcontainer Development] - ShrinkWrapDeployer

by Ales Justin

Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion "ShrinkWrapDeployer" To view the discussion, visit: http://community.jboss.org/message/540427#540427 -------------------------------------------------------------- I still don't see why it should be part of deployers. Why not make it a top level project in jbossas/projects? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540427#540427] Start a new discussion in JBoss Microcontainer Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Microcontainer Development] - ShrinkWrapDeployer

by Andrew Rubinger

Andrew Rubinger [http://community.jboss.org/people/ALRubinger] replied to the discussion "ShrinkWrapDeployer" To view the discussion, visit: http://community.jboss.org/message/540422#540422 -------------------------------------------------------------- MC bean enabling native deployment of ShrinkWrap archives. Should be centralized because it'll be used in EmbeddedAS, Embedded EJB3, Arquillian, etc. In a nutshell, this: /** * Deployer for ShrinkWrap {@link Archive} types. End-user * view to adapt archives directly into the Virtual Deployment * Framework. * * @author <a href="mailto:andrew.rubinger@jboss.org">ALR</a> * @version $Revision: $ */ public interface ShrinkWrapDeployer { //-------------------------------------------------------------------------------------|| // Contracts --------------------------------------------------------------------------|| //-------------------------------------------------------------------------------------|| /** * Deploys the specified archives into the Virtual Deployment Framework * as an atomic operation. * * @param archives The archives to deploy * @throws IllegalArgumentException If the archives are not specified (null) * @throws DeploymentException If an error occurred in deployment */ void deploy(Archive<?>... archives) throws IllegalArgumentException, DeploymentException; /** * Undeploys the specified archives from the Virtual Deployment Framework. Each * archive must have been previously deployed in via this {@link ShrinkWrapDeployer} * instance, else it will be ignored and logged as a warning. * * @param archives The archives to undeploy * @throws IllegalArgumentException If the archives are not specified * @throws DeploymentException If an error occurred during undeployment */ void undeploy(Archive<?>... archives) throws IllegalArgumentException, DeploymentException; } S, ALR -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540422#540422] Start a new discussion in JBoss Microcontainer Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

[JCA Development] - Security integration for JCA 1.6

by Jesper Pedersen

Jesper Pedersen [http://community.jboss.org/people/jesper.pedersen] created the discussion "Security integration for JCA 1.6" To view the discussion, visit: http://community.jboss.org/message/540410#540410 -------------------------------------------------------------- Scott, if you have time to take a look at the security requirements for the JCA 1.6 implementation that would be great. Here are a couple of pointers to get started * Chapter 16 in the specification - it describes requirements plus use-cases * Investigate security infrastructure in AS/trunk to align requirements * Create a deisgn for a simple security domain for the standalone project * Start with a test case where a Work instance uses a SecurityContext * and build from there There are a couple of other requirements, since this is one of the big integration points for the project * Test cases covering the use-cases described * A chapter in the JCA Developer Guide describing the setup and integration Keep in mind that this is one of the places where we need an internal SPI such that we can integrate with the standalone setup and the setup used in JBoss Application Server. You +can+ take a look at the security integration in the current JCA implementation inside AS, but I want a clean design with well-defined integration points - and a documented way of locating the needed information. For the first implementation of the SPI for the standalone part I would suggest that you start with a simple setup using properties files - similar to the UsersRolesLoginModule idea in JBossSX. And then build from there... The principal mapping tool could just be a file too... And start with the requirements for the WorkManager (watch out for nested Work submissions with different SecurityContexts) - and save the MessageEndpoints for later. The code should be located in the core/ module - and feel free to use EmbeddedJCA and the ShrinkWrap support for the test cases. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540410#540410] Start a new discussion in JCA Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Microcontainer Development] - ShrinkWrapDeployer

by Ales Justin

Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion "ShrinkWrapDeployer" To view the discussion, visit: http://community.jboss.org/message/540360#540360 -------------------------------------------------------------- What would be the benefit of this? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540360#540360] Start a new discussion in JBoss Microcontainer Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - JBPM-2537

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "JBPM-2537" To view the discussion, visit: http://community.jboss.org/message/540355#540355 -------------------------------------------------------------- I just wondering if in this scenario task should be completed. To me it sounds more like cancellation than completion. Especially if we are considering some kind of reviews of process and its history. Because if you complete a task that no one has taken any action on that could be confusing. But that is my opinion... -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540355#540355] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - JBPM-2537

by Huisheng Xu

Huisheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "JBPM-2537" To view the discussion, visit: http://community.jboss.org/message/540349#540349 -------------------------------------------------------------- Hi Sebastian, Because of an already fixed issue, Tom move dbSession.delete(task) from TaskActivity.signal() to TaskImpl.complete(). So if we call TaskService.completeTask() and signal the related execution. The task will alway be deleted before execution.signal(). So we could use it to judge who are calling signal() method. If we can not find the task for current execution, it will be the normal way, and task had been completed normally. If there is still a task for current execution. This task must be out of date. Here is the issue. https://jira.jboss.org/jira/browse/JBPM-2607 https://jira.jboss.org/jira/browse/JBPM-2607 Yes, I know we still cannot tell whether there is a timerout event occurred and it is surely a design problem. But directly add a timeout() to ExternalActivityBehaviour is not a good design, too. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540349#540349] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Wiki Portlet Development] - Status and roadmap for JBoss Wiki

by Piergiorgio Lucidi

Piergiorgio Lucidi [http://community.jboss.org/people/piergiorgiolucidi] replied to the discussion "Status and roadmap for JBoss Wiki" To view the discussion, visit: http://community.jboss.org/message/540345#540345 -------------------------------------------------------------- Unfortunately now we have no news about this. We are deciding to implement a new wiki portlet or try to import the eXo wiki portlet. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/540345#540345] Start a new discussion in JBoss Wiki Portlet Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2010