March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBMESSAGING-26) Standalone Messaging configuration.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=comments#action_123... ] Ovidiu Feodorov commented on JBMESSAGING-26: -------------------------------------------- To answer my question above: Yes, we do. > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Alex Pinkin > Fix For: 1.2.1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-728) DSLs to be loaded into suggestion completion engine

by Michael Neale (JIRA)

DSLs to be loaded into suggestion completion engine --------------------------------------------------- Key: JBRULES-728 URL: http://jira.jboss.com/jira/browse/JBRULES-728 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Edson Tirelli -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-908) Code-Cleanup: use generic containers to remove type-casts

by Stefan Huehner (JIRA)

Code-Cleanup: use generic containers to remove type-casts --------------------------------------------------------- Key: EJBTHREE-908 URL: http://jira.jboss.com/jira/browse/EJBTHREE-908 Project: EJB 3.0 Issue Type: Patch Reporter: Stefan Huehner Priority: Optional Attachments: jboss_generics1.diff Hi, attached patch specifies severals containers as typed containers to remove type-casts of i.e. <container>.get -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-907) Code-Cleanup: remove unused imports

by Stefan Huehner (JIRA)

Code-Cleanup: remove unused imports ----------------------------------- Key: EJBTHREE-907 URL: http://jira.jboss.com/jira/browse/EJBTHREE-907 Project: EJB 3.0 Issue Type: Patch Reporter: Stefan Huehner Priority: Trivial Attachments: jboss_imports2.diff Hi, this patch (against current trunk) removes some unused import statements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4188) Code-Cleanup: remove unused imports

by Stefan Huehner (JIRA)

Code-Cleanup: remove unused imports ----------------------------------- Key: JBAS-4188 URL: http://jira.jboss.com/jira/browse/JBAS-4188 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Test Suite Reporter: Stefan Huehner Priority: Trivial Attachments: jboss_imports1.diff Hi, this patch (against current trunk) removes some unused import statements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1314) no clean shutdown of jboss portal

by Prabhat Jha (JIRA)

no clean shutdown of jboss portal --------------------------------- Key: JBPORTAL-1314 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1314 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Prabhat Jha During shutdown of a server that has jboss-portal-ha.sar deployed, I see following error. We need to see how this can be suppressed if it's a harmless error. 14:06:21,343 ERROR [JDBCExceptionReporter] You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceExceptio nectionFactory is null.) 14:06:21,343 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session org.hibernate.exception.GenericJDBCException: Cannot open connection at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:420) at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144) at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:94) at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:87) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-2315) Create an automated test for JBAS-2314

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2315?page=all ] Brian Stansberry updated JBAS-2315: ----------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.GA) > Create an automated test for JBAS-2314 > -------------------------------------- > > Key: JBAS-2315 > URL: http://jira.jboss.com/jira/browse/JBAS-2315 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-4.2.1.CR1 > > > I currently test the JBAS-2314 fix manually; need to automate. Basically need to add a war to web-sso.ear that has secured resources but no authenticator configured. Test should access the normal sso test war on one server, then the other, and then on the 2nd server access the war w/o authenticator, confirming that no 403 is seen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-340) Create maven plugin to deploy artifacts to the non-maven jboss repository.

by Paul Gier (JIRA)

Create maven plugin to deploy artifacts to the non-maven jboss repository. -------------------------------------------------------------------------- Key: JBBUILD-340 URL: http://jira.jboss.com/jira/browse/JBBUILD-340 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: MavenBuild 1.2 Create a maven plugin that will bind to the deploy phase to deploy to the jboss repository. When a developer is ready to deploy a project, the required artifacts should be deployed to both the maven2 repository, and the non-maven repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4113) jbossweb 2.0.0

by Scott M Stark (JIRA)

jbossweb 2.0.0 -------------- Key: JBAS-4113 URL: http://jira.jboss.com/jira/browse/JBAS-4113 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Scott M Stark Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.Beta2 We need a release of the jbossweb 2.0.x to replace the 2.0.0.snapshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-462) the token's subProcessInstance attribute is not set on subprocess-end event if a process is loaded from db

by Jesse Sweetland (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-462?page=comments#action_12355521 ] Jesse Sweetland commented on JBPM-462: -------------------------------------- I'm using 3.1.2 and I noticed that subProcessInstance is set to null when a process completes. The superProcessToken value of the sub process is still intact. Is this the intended behavior? > the token's subProcessInstance attribute is not set on subprocess-end event if a process is loaded from db > ---------------------------------------------------------------------------------------------------------- > > Key: JBPM-462 > URL: http://jira.jboss.com/jira/browse/JBPM-462 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1, jBPM 3.0.2 > Reporter: Eduardo Jimenez > Assigned To: Tom Baeyens > Fix For: jBPM 3.1 > > > Token.subprocessinstance is not a persistent field, which means that if the subprocess is started, saved, then loaded in a different hibernate session later, the token.subprocessinstance field is null, which means that if you have an action on a subprocess-end event, its not going to know which subprocess ended. > making the list of subprocesses is great, but it doesn't solve this problem. My gut feeling is that this should be treated as it is treated during subprocess creation: > Code: > public void execute(ExecutionContext executionContext) { > Token superProcessToken = executionContext.getToken(); > // create the subprocess > ProcessInstance subProcessInstance = new ProcessInstance(subProcessDefinition); > // bind the subprocess to the super-process-token > superProcessToken.setSubProcessInstance(subProcessInstance); > subProcessInstance.setSuperProcessToken(superProcessToken); > // fire the subprocess created event > fireEvent(Event.EVENTTYPE_SUBPROCESS_CREATED, executionContext); > ..... > > See how the superProcessToken gets a nice setSubProcessInstance? That way the subprocess-created event knows which subprocess was created. > The current code on notifySubProcessEnd is: > Code: > public void notifySubProcessEnd(ProcessInstance subProcessInstance) { > Token superProcessToken = subProcessInstance.getSuperProcessToken(); > ExecutionContext executionContext = new ExecutionContext(superProcessToken); > // feed the readable variables > if ((variableAccesses != null) && (!variableAccesses.isEmpty())) { > .... > .... > } > // feed the readable variables > fireEvent(Event.EVENTTYPE_SUBPROCESS_END, executionContext); > .... > > I think it is very reasonable to do instead > Code: > public void notifySubProcessEnd(ProcessInstance subProcessInstance) { > Token superProcessToken = subProcessInstance.getSuperProcessToken(); > > superProcessToken.setSubProcessInstance(subProcessInstance); > ExecutionContext executionContext = new ExecutionContext(superProcessToken); > // feed the readable variables > if ((variableAccesses != null) && (!variableAccesses.isEmpty())) { > .... > .... > } > // fire the subprocess ended event > fireEvent(Event.EVENTTYPE_SUBPROCESS_END, executionContext); > .... > > In this way, the subprocess-end event will pass a context where the token correctly contains the subprocess instance even if being loaded after being persisted while the subprocess was going on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

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