[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3553) context path of demos needs to be predictable

Pete Muir (JIRA) jira-events at lists.jboss.org
Mon Oct 13 17:25:20 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBSEAM-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed JBSEAM-3553.
-----------------------------

    Resolution: Rejected


All archives are deployed as jboss-seam-appName AFAIK. I don't see how we can fix the context paths without removing the seam prefix, which risks collisions with user apps.

> context path of demos needs to be predictable
> ---------------------------------------------
>
>                 Key: JBSEAM-3553
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3553
>             Project: Seam
>          Issue Type: Task
>          Components: Examples
>    Affects Versions: 2.1.0.CR1
>            Reporter: Dan Allen
>             Fix For: 2.1.1.CR1
>
>
> I can never figure out what the context path is of the example application I deploy. It needs to be consistent with the name of the folder. For instance, the context path for dvdstore should be dvdstore, not seam-dvd. We can, of course, use a standard suffix if we need to differentiate between an EAR and a WAR. For instance, the WAR can be dvdstore and the EAR can be dvdstore-ee or something. But it has to be consistent. Take seamspace for example. At various times it has been seam-space, seamspace, jboss-seam-space, and jboss-seamspace. This is like a game of whack-a-mole.

-- 
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

        



More information about the seam-issues mailing list