Bug 1042789

Summary:	Inform a user that a kjar cannot be uploaded due to missing dependencies instead of throwing IllegalArgumentException: number of transferred bytes cannot be negative
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Ivo Bek <ibek>
Component:	Business Central	Assignee:	manstis
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ivo Bek <ibek>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	dhoffman, etirelli, manstis, mbaluch, trikkola, vigoyal
Target Milestone:	ER1
Target Release:	6.0.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Fixed Issue Summary: The system used to throw an IllegalArgumentException when a kjar with missing dependencies was uploaded. This message was not very clear about the actual error and it was often misleading. The system now informs the user with a more helpful error message when a kjar with missing dependencies is uploaded. Known Issue Summary: The system throws an IllegalArgumentException when a kjar with missing dependencies is uploaded. This message is not clear about the actual error and is misleading. The system should instead let the user know that the kjar that they have just uploaded is missing some dependencies.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 19:51:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ivo Bek 2013-12-13 11:58:56 UTC

Description of problem:

This bug is based on the discussion in BZ 1018220, which was considered not a bug but we agreed that the user should be informed about the problems with dependencies more clearly.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 manstis 2014-03-03 10:20:12 UTC

I tried to replicate the IllegalArgumentException however was always presented with a (more) helpful error message (using the project attached to https://bugzilla.redhat.com/show_bug.cgi?id=1018220).

On investigation this BZ appears to have been resolved by that I reference in the "See also" section.

Comment 2 Ivo Bek 2014-05-05 08:13:11 UTC

Verified in BPMS 6.0.2.ER2