[ http://wso2.org/jira/browse/WSAS-689?page=all ]
Afkham Azeez resolved WSAS-689.
-------------------------------
Resolution: Not a bug
It is ok to keep the configuration. If you add the jars and restart the server,
the service will no longer be faulty. Also several services can share the same
configuration hence it is incorrect to delete a shared configuration. Let's
keep the implementation simple.
> EJBservice: Faulty ejb service provider configurations are not removed when
> deleting services
> ---------------------------------------------------------------------------------------------
>
> Key: WSAS-689
> URL: http://wso2.org/jira/browse/WSAS-689
> Project: WSO2 WSAS
> Issue Type: Bug
> Environment: winxp, jdk15, WSAS-2.2-qabuild6
> Reporter: Charitha Kankanamge
> Assigned To: sumedha rubasinghe
> Priority: Critical
>
> Steps to reproduce:
> ===============
> 1. Deploy an ejb service (Make it faulty by removing some app server specific
> jars)
> 2. Remove the faulty ejb service
> 3. ejb provider configuration is added to the existing configuration list
> There is no action to remove the configuration if it is faulty. Therefore,
> the faulty configuration should be automatically removed when deleting the
> faulty service.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
