Issue Details (XML | Word | Printable)

Key: GLASSFISH-19533
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: naman_mehta
Reporter: Anissa Lam
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

admin-object-resource does not take "domain" as target like any other resource

Created: 14/Jan/13 10:46 PM   Updated: 11/Feb/13 09:42 AM   Resolved: 11/Feb/13 09:42 AM
Component/s: jca
Affects Version/s: 4.0_b70
Fix Version/s: 4.0_b75

Time Tracking:
Not Specified

Participants: Anissa Lam and naman_mehta

 Description  « Hide

For every type of resource, the creation or delete will take "domain" as the target, except admin-object-resource.
In console, we rely on this to work properly.
we will

  • create a resource with "domain" as target
  • create all resource-ref appropriately. if DAS only, create the resource-ref for 'server', otherwise, whatever the user choose. And user may select to not have any target specified.

However, error thrown if we do this with 'admin-object-resource'. This is a long time bug, and console work around it using "server-config" as its target instead of 'domain'. This doesn't make sense, but kind of work. There thus a <resource-ref> under server-config. Console code want to remove this workaround and keep domain.xml correct.

Anissa Lam added a comment - 14/Jan/13 11:11 PM

This workaround also stops working.
resource-ref that get created under <server-config> no longer get deleted, although the request return success. As a result, there are obsoleted <resource-ref> under <server-config> that can't be removed.

naman_mehta added a comment - 11/Feb/13 09:42 AM

Fixed the issue related to resource-ref removal when resource is removed.

As discussion on the mail, domain is not going to be valid target for admin-object resource, closing this issue.