This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 75712 - Cannot edit web app cache mapping as a policy
Summary: Cannot edit web app cache mapping as a policy
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
: 75912 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-04-28 19:59 UTC by _ pcw
Modified: 2006-05-29 19:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stack trace (3.57 KB, text/plain)
2006-04-28 19:59 UTC, _ pcw 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ pcw 2006-04-28 19:59:03 UTC 
IllegalArgumentException when attempting to edit a cache mapping policy in the
sun configuration editor.

New Web App
Open sun-web.xml in config editor.
Go to Cache tab, Cache Mapping sub-tab.
Add a cache mapping entry.
Select policy radio button and click <Edit Policy>

Exception...
ava.lang.IllegalArgumentException: The specified value () does not match one of
the enumerated values: context.attribute request.header request.parameter
request.cookie request.attribute session.attribute 
	at org.netbeans.modules.schema2beans.BeanProp.setAttributeValue(BeanProp.java:1259)
	at org.netbeans.modules.schema2beans.BaseBean.setAttributeValue(BaseBean.java:626)
	at
org.netbeans.modules.j2ee.sun.dd.impl.web.model_2_5_0.CacheMapping.setTimeoutScope(CacheMapping.java:306)
...
Comment 1 _ pcw 2006-04-28 19:59:38 UTC 
Created attachment 30138 [details]
stack trace
Comment 2 _ pcw 2006-04-28 20:02:02 UTC 
This is a regression that was caused when we upgraded the sunddapi module to use
the new ENTITY support in schema2beans.  The code is attempting to set a blank
value in an entity field that does not allow blank values (previously this
requirement was not enforced at the bean level and the output XML was correct
for this specific case).  We have to tighten up the code so that it uses only
the exact values the entity allows.
Comment 3 _ pcw 2006-05-22 22:38:02 UTC 
Fixed.
Comment 4 _ pcw 2006-05-29 19:47:27 UTC 
*** Issue 75912 has been marked as a duplicate of this issue. ***