[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
18 years, 11 months
[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
18 years, 11 months
[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
18 years, 11 months
[JBoss JIRA] Created: (JBPM-715) Implement runtime automagically generated forms
by Ronald van Kuijk (JIRA)
Implement runtime automagically generated forms
-----------------------------------------------
Key: JBPM-715
URL: http://jira.jboss.com/jira/browse/JBPM-715
Project: JBoss jBPM
Issue Type: Feature Request
Components: Web Interface
Environment: n/a
Reporter: Ronald van Kuijk
Assigned To: Tom Baeyens
Priority: Minor
Fix For: jBPM 3.2
As long as it is not possible to generate an .xhtml file from the gpd for a task, it should be possible to use a designed process without the need to create custom forms.
Initially this would be identical to the 3.1 automagical forms (not taking into account the variable type) but it should some day.
Taking the variable type into account would be possible if the variable already exists in the process instances, but if it is initially filled via a type agnostic ui, it will always be string. If it is set via the api, we could take it into account.
--
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
18 years, 11 months
[JBoss JIRA] Created: (JBMAIL-245) getBoundary() in MessageData crashes if no Content-Type header is present
by Pat Osterday (JIRA)
getBoundary() in MessageData crashes if no Content-Type header is present
-------------------------------------------------------------------------
Key: JBMAIL-245
URL: http://jira.jboss.com/jira/browse/JBMAIL-245
Project: JBoss Mail
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Pat Osterday
Assigned To: Andrew Oliver
In the getBoundary() method in MessageData, I think the line:
String[] header = getHeader("Content-Type").split("\\r\\n");
Should be moved into the try/catch. If a message doesn't have a Content-Type, the method crashes.
Not sure how the writeMessage in CmdRETR in the pop3 handlers would handle this, but I'm using similar code to read messages via a servlet and this issue just popped up for us.
Another option would be something like this in the beginning of the method:
String ctHeader = getHeader("Content-Type");
String[] header = null;
if (ctHeader != null) {
header = ctHeader.split("\\r\\n");
} else {
return null;
}
--
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
[JBoss JIRA] Created: (JBMAIL-244) Fetching mail with MalformedHeader from POP3 server
by Ryan Maloney (JIRA)
Fetching mail with MalformedHeader from POP3 server
----------------------------------------------------
Key: JBMAIL-244
URL: http://jira.jboss.com/jira/browse/JBMAIL-244
Project: JBoss Mail
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBoss application server 4.0.4-CR2 running on Windows XP Profesional SP2
Reporter: Ryan Maloney
Assigned To: Andrew Oliver
Enabled fetchmail and added a pop3 account. Manually invoked the pop() method via the mx-console and received the following:
[Top part of the stack trace]
INFO [org.jboss.mail.fetchmail.Popper] Found 104 messages (0) new ones
INFO [org.jboss.mail.fetchmail.Popper] Trying to get message 0
INFO [org.jboss.mail.fetchmail.Popper] Message 0 Subject: EMAIL SUBJECT REMOVED
ERROR [org.jboss.mail.fetchmail.Popper]
org.jboss.mail.message.MalformedHeaderException: Malformed Header:
This is a multi-part message in MIME format.
[end snippet]
Mail retrieval ended immediately thereafter.
I have sent the offending header to acoliver(a)jboss.com
--
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