Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 899175 (JBEWS-233)

Summary: EWS on Windows: Reorganize directory structure.
Product: [JBoss] JBoss Enterprise Web Server 1 Reporter: Ondřej Žižka <ozizka>
Component: unspecifiedAssignee: Permaine Cheung <pcheung>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: EWS 1.0.1CC: mmillson, rajesh.rajasekaran
Target Milestone: ---   
Target Release: EWS 1.0.1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEWS-233
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-12 01:09:45 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:
Embargoed:
Attachments:
Description Flags
windows.jpg
none
wininstall.txt none

Description Ondřej Žižka 2010-02-01 16:10:20 UTC 
Date of First Response: 2010-02-02 11:30:48
project_key: JBEWS

Windows users are not used to the unix-like directory structure.
Having the distribution archive organized into folders like /bin /sbin /var/log/httpd/log etc. is not pleasing at all. More, it makes the product quite hard to configure (e.g. starting Tomcat as a service needs copying files across these directories and "manually" creating the service (i.e. not using service.bat).

Please reorganize the dirs as they are in the Windows distributions of the upstream project, and separate them by app at the root level (i.e. httpd/, tomcat5/, tomcat6/ or so).
Comment 1 Ondřej Žižka 2010-02-01 16:10:52 UTC 
Link: Added: This issue depends JBQA-3040
Comment 2 Ondřej Žižka 2010-02-01 16:11:17 UTC 
Link: Added: This issue is incorporated by JBQA-3040
Comment 3 Ondřej Žižka 2010-02-01 16:14:06 UTC 
Link: Removed: This issue depends JBQA-3040
Comment 4 Mladen Turk 2010-02-02 16:30:48 UTC 
This means creating a completely new project.
It breaks the initial premise of reusing RHEL artifacts for producing platform binaries.

I won't do it.
Comment 7 Mike Millson 2010-02-03 01:43:34 UTC 
Attachment: Added: windows.jpg
Comment 8 Mladen Turk 2010-02-03 15:24:28 UTC 
Quick install howto
Comment 9 Mladen Turk 2010-02-03 15:24:28 UTC 
Attachment: Added: wininstall.txt
Comment 10 Mladen Turk 2010-02-03 15:34:48 UTC 
Discussion what is preferred layout is irrelevant, if we document that layout well.

The same layout is on Solaris as well, and the reason for such layout is to reuse the RHEL artifacts.
That was the initial premise of the EWS, so if we change the layout it will require to change all the configuration
files from RHEL which will make multiple points of failure and require maintaining them separately.

At the end the product name has 'Red Hat' as the prefix, and as such it doesn't have
to follow the community layouts, because it is not community version.

Also we cannot just forget about that layout and use community version layout because
that would require to use the Operating System libraries for openssl, ldap and stuff which
would again lead to something completely different.
Comment 12 Ondřej Žižka 2010-02-03 22:31:47 UTC 
Rajesh summed it up exactly:
Take this report rather as a feature request, and mark it Won't fix if not worth the work.
Comment 13 Permaine Cheung 2010-02-04 15:47:46 UTC 
Marking as won't fix as we have specific install instructions for our distribution, it's not worth the work.
Comment 14 Ondřej Žižka 2010-02-12 01:08:44 UTC 
(Reopening only to fill fhe Component and Affected ver.)
Comment 15 Karel Piwko 2010-09-23 08:15:50 UTC 
Link: Added: This issue related JBPAPP-5018
Comment 16 Karel Piwko 2011-06-03 12:08:10 UTC 
Link: Added: This issue relates to JBPAPP-6665