[
https://jira.jboss.org/jira/browse/JBSEAM-3119?page=com.atlassian.jira.pl...
]
Frank Cornelis commented on JBSEAM-3119:
----------------------------------------
Why has such an important feature (actually it's a bug) been rescheduled once again
from 2.1.2.CR1 to 2.2.0.CR1 and now to 2.2.1.CR1 in favor of stupid teaser/tutorial
features???
This missing feature/bug renders JBoss Seam completely useless in enterprise application
architectures where you have multiple web application portals per enterprise application.
For example: one user portal and an admin portal.
Last night I was discussing JBoss/OSS issues like this one with a fellow developer and I
must say that I'm not the only one convinced of a hidden agenda.
Now I can understand that RedHat wants to sell as much Linux support as possible. Thus by
making sure that one JBoss AS can host only one Seam web application at the same time,
you're almost forcing people into having multiple OS instances using some
virtualization. This certainly increases support income on the RedHat part. So in the
short-term such a strategy perfectly works.
The problem is that I'm writing public tenders for the Belgian government and I'm
about to exclude JBoss Seam from the list of allowed technologies because of this issue
still not being fixed.
Multiple WAR in EAR verification, example, and document
-------------------------------------------------------
Key: JBSEAM-3119
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3119
Project: Seam
Issue Type: Feature Request
Components: Documentation Issues, Examples, Platform interoperability
Affects Versions: 2.1.0.A1
Reporter: Jay Balunas
Assignee: Norman Richards
Fix For: 2.2.1.CR1
Attachments: admin-dvdstore.diff, multi-war-appname1.diff, multi-war-wip-v2.diff,
multi-war-wip.diff, multiple-wars.diff
Create an example of two seam WAR applications inside of an EAR. There has been quite a
bit of forum traffic on the subject and it would be good to nail down an example and
document. There may also be errors and other issue that need to be worked out.
An admin console type application to the standard booking application may be a good way
to go. It would be a real world/useful example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira