August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3398) Non exploded sar containing war cannot undeploy the war file properly

by Julien Viet (JIRA)

Non exploded sar containing war cannot undeploy the war file properly --------------------------------------------------------------------- Key: JBAS-3398 URL: http://jira.jboss.com/jira/browse/JBAS-3398 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1, JBossAS-4.0.3 Final Environment: JBoss-4.0.4.GA MacOSX Tiger Java 1.4.2 Reporter: Julien Viet Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.GA A sar file containing a war file non exploded is dropped in AS before startup. Start JBoss Shutdown JBoss The MainDeployer wants to stop() / destroy() the war file. The Web deployer is already gone and it produces an javax.management.InstanceNotFoundException when it tries to stop() / destroy() the war deployer Because the war is nested in a sar file, the web deployer is undeployed before the sar containing the war is undeployed. Note : this does not happen with exploded sar (like http invoker sar that contains the invoker.war) because the war is added to the MainDeployer.deploymentList list. This does not happen with non exploded because the war file is not in the local directory but rather in tmp and thus does not get added to the deployment list. Here are some field values : the string used to discriminate wether it's in local or tmp - file:/Users/julien/java/jboss-4.0.4.GA/server/default/tmp/deploy/ a war in non exploded sar - file:/Users/julien/java/jboss-4.0.4.GA/server/default/tmp/deploy/tmp51485jboss-portal.sar-contents/portal-core.war invoker.war in exploded sar - file:/Users/julien/java/jboss-4.0.4.GA/server/default/deploy/http-invoker.sar/invoker.war/ -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-695) Have the GPD add all default attributes to nodes instead of leaving them out

by Ronald van Kuijk (JIRA)

Have the GPD add all default attributes to nodes instead of leaving them out ---------------------------------------------------------------------------- Key: JBPM-695 URL: http://jira.jboss.com/jira/browse/JBPM-695 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Environment: N/A Reporter: Ronald van Kuijk Assigned To: Tom Baeyens It would be nice if the GPD added the defaults of attributes to nodes (e.g. task-end="false" on a tasknode) this way, even with no graphical support, users often think further, search for it etc, that it would help (even for me!!! ;-)) -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3473) Fix DistributedStateImpl.nodeRemove

by Brian Stansberry (JIRA)

Fix DistributedStateImpl.nodeRemove ----------------------------------- Key: JBAS-3473 URL: http://jira.jboss.com/jira/browse/JBAS-3473 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta AFAICT, this is not correct. Key/value pairs are stored in the category node's data map; nodeRemoved treats things as if each key is its own node. Actually, I think the node per key approach is correct, until TreeCacheListener can provide info on what data was changed. Also, remove() itself notifies listeners of a removal, and then the listener does as well. Needs to be one or the other; probably nodeRemoved() as that gets called for both local and remote removes. -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-698) gpd is not working with latest version of commons-fileupload jar.

by Olivier Debels (JIRA)

gpd is not working with latest version of commons-fileupload jar. ----------------------------------------------------------------- Key: JBPM-698 URL: http://jira.jboss.com/jira/browse/JBPM-698 Project: JBoss jBPM Issue Type: Bug Components: Graphical Process Designer Reporter: Olivier Debels Assigned To: Tom Baeyens When trying to used the graphical process designer with the latest version of commons-upload (version 1.1.1) it is not longer possible to deploy process definitions. You get the exception 'The process definition was rejected because no multiplart boundary was found'. The reason is that the gpd is using a ',' to separate its content type (in the url used to trigger the upload servlet) where it must be a ';' according to RFC1341. So instead of 'multipart/form-data,boundary=AaB03x' it must be 'multipart/form-data;boundary=AaB03x'. The webapp must work with the latest version of commons-fileupload. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-699) build.xml needs to be modified for jbpm to build successfully

by Prabhat Jha (JIRA)

build.xml needs to be modified for jbpm to build successfully ------------------------------------------------------------- Key: JBPM-699 URL: http://jira.jboss.com/jira/browse/JBPM-699 Project: JBoss jBPM Issue Type: Task Reporter: Prabhat Jha Assigned To: Koen Aers Priority: Minor To build jBPM successfully, I had to make the following changes. A. Add the constructs to create missing directories under target "download-eclipse" in jbpm.dist\build.xml <mkdir dir="${local-repository}/${eclipse-folder}"/> <mkdir dir="${local-repository}/${webtools-folder}"/> <mkdir dir="${local-repository}/${emf-folder}"/> <mkdir dir="${local-repository}/${gef-folder}"/> <mkdir dir="${local-repository}/${jem-folder}"/> B. Modify the <import file > under jbpm.dist\build\projects\docs\gpd.userguide as <import file="../../docbook-support/support.xml" /> Can you check in these changes in CVS? I am not sure if you are the right person. Thanks, Prabhat -- 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, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-727) add support for adding Action to Nodes without adding Event

by mehmet bozok (JIRA)

add support for adding Action to Nodes without adding Event ----------------------------------------------------------- Key: JBPM-727 URL: http://jira.jboss.com/jira/browse/JBPM-727 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Reporter: mehmet bozok Assigned To: Tom Baeyens We are extending some parts of GDP in our project, and we need to add Action to Node without adding an Event then show this Aciton on outline tree view. Althought there is a mechanism to add a single Action to Nodes(not in GDP menu but implemented in org.jbpm.ui.model.Node), it is not shown at outline tree view. In order to make Action appear on tree view as a Node child we needed to add a menu option, and handle ActionTreeEditPart and NodeTreeEditpart relation in a different way. (not by changing GPD code, but instantiating editparts then reflecting org.eclipse.gef.AbstractEditPart and calling its protected methods which is not a very safe way.) Therefore it seems neccesary to change iplementation so that single Action (also providing which Action to add) can be added to Node and shown in outline tree view. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-752) Look into using JBC Marshaller implementations for responses as well as requests

by Brian Stansberry (JIRA)

Look into using JBC Marshaller implementations for responses as well as requests -------------------------------------------------------------------------------- Key: JBCACHE-752 URL: http://jira.jboss.com/jira/browse/JBCACHE-752 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Replication Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0 In JGroups 2.4 the ability to use a Marshaller for responses as well as requests was added. At some point JGroups may require that the *same* marshaller instance handle both. JBC's current marshallers can't do this; need to look into what it would take to do it. Should be simple, as RPC responses in JBC are either null, an exception, or a byte[] (for RPC based state transfer). -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-115) Split (Esb)Util and group common utility methods.

by Arvinder Singh (JIRA)

Split (Esb)Util and group common utility methods. ------------------------------------------------- Key: JBESB-115 URL: http://jira.jboss.com/jira/browse/JBESB-115 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Arvinder Singh Assigned To: Arvinder Singh Priority: Minor Fix For: 4.0 Split (Esb)Util and group common utility methods. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-719) Create ws dir, resources, build.xml under the project root

by Ronald van Kuijk (JIRA)

Create ws dir, resources, build.xml under the project root ---------------------------------------------------------- Key: JBPM-719 URL: http://jira.jboss.com/jira/browse/JBPM-719 Project: JBoss jBPM Issue Type: Feature Request Environment: n/a Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Minor Fix For: jBPM 3.2 Create <jbpm.home>/ws and all relevant subdirs according to what already exists (take console as an example) Create a build.xml file according to what already exists (take console as an example) Initially add jbossws from <jboss.home> if set, see other issue for getting jbossws in the 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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-720) create a schema for the jbpm ws frontend

by Ronald van Kuijk (JIRA)

create a schema for the jbpm ws frontend ---------------------------------------- Key: JBPM-720 URL: http://jira.jboss.com/jira/browse/JBPM-720 Project: JBoss jBPM Issue Type: Sub-task Environment: n/a Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Minor Fix For: jBPM 3.2 It should work with jboss ws 1.0.2.GA (or all since 1.0?) -- 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, 6 months

1
2
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 August 2006