[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1967) Implement in memory webapp deployment

[Richard Opalka (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBWS-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12430005#action_12430005 ] 

Richard Opalka commented on JBWS-1967:
--------------------------------------

I resolved JBAS-5257 as won't fix because it is not necessary to be fixed to be TCK5 compliant.
Endpoint.publish(), Endpoint.unpublish() is faulty by design IMHO. 
It doesn't make sense to be able to publish POJOs to different web contexts.

Here are top two reasons why I think it is broken and hence excluded from TCK5 tests:
 * security issue (how to configure java security for such ugly published endpoints where e.g. Security Manager is turned on)?
 * design problem (why web archive should be able to publish another web/ejb archive)?

I have no solution to this problem:(

> Implement in memory webapp deployment
> -------------------------------------
>
>                 Key: JBWS-1967
>                 URL: https://jira.jboss.org/jira/browse/JBWS-1967
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>            Reporter: Heiko Braun
>            Assignee: Richard Opalka
>
> Scott wrote:
> The tomcat layer is being driven by the WebMetaData/JBossWebMetaData now, so any modification by the ws deployers should be done as input into a deployer like MergedJBossMetaDataDeployer does for the ejb metadata. I'd like to get this cleaned up for jbossas 5.0.0.CR1 when the war deployer is cleaned up.

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