Bug 780190 (SOA-2568)

Summary:	adminshell.bat cannot read script from stdin
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Aleksandar Kostadinov <akostadinov>
Component:	EDS	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.ER4
Target Milestone:	---
Target Release:	5.1.0 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2568
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	windows
Last Closed:	2010-11-16 14:45:27 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 Aleksandar Kostadinov 2010-11-11 06:00:24 UTC

project_key: SOA

On windows adminshell doesn't read script if supplied on stdin. It looks like it is reading from terminal (unlike adminshell on linux). I see that one can supply expression as first argument to adminshell but it seems to accept only a single expression and additionally complex expressions are a hell to escape properly.

Assuming adminshell is intended to be used for automating administrative tasks, it needs a straightforward way to execute scripts non-interactively so current behavior on windows needs to be fixed.

Comment 1 Aleksandar Kostadinov 2010-11-11 06:01:02 UTC

Link: Added: This issue Cloned to SOA-2569

Comment 2 John Graham 2010-11-16 14:45:27 UTC

See linked project JIRA for discussion

Comment 3 Aleksandar Kostadinov 2010-11-16 17:16:47 UTC

See my comment in the linked project jira.
btw "Cannot Reproduce Bug" suggests that you can execute scripts like "adminshell.bat < myscript" so perhaps "rejected" would better represent your decision given you have provided another way for executing scripts non-interactively.

Thanks

Comment 4 Aleksandar Kostadinov 2010-11-21 03:10:36 UTC

As I have commented on TEIID-1355, the problem is not easy to fix even less within the given timeframe and is not critical for SOA-P so leaving this SOA-P jira as closed.