|
If you were logged in you would be able to see more operations.
|
|
I have a native Java repository with RDF Schema inferencing enabled. In the Sesame workbench web GUI I viewed the Contexts and saw 2. Then I added a couple triples with a new, unique context. After the load finished I refreshed the Contexts page expecting to see 3, but at that point the workbench context page still only showed the original 2. I thought the page might be cached in my browser, so I opened a different browser on the same URL, and there the expected number of contexts is shown! So it's a caching problem. I believe the server (servlet?) is making an inappropriate determination when the browser requests the URL. It should always regenerate the full page. I realize this may clobber some optimizations and such. I think this is a fairly common issue on servers for pages with dynamically generated content that are not yet AJAX. This issue probably affects all the workbench pages, not just Context. Thanks for listening!
|
|
|
Change by Jeen Broekstra [17/Sep/12 10:49 AM]
|
| Field |
Original Value |
New Value |
|
Fix Version/s
|
|
2.7.0
[ 10630
]
|
|
Assignee
|
Arjohn Kampman
[ arjohn
]
|
Jeen Broekstra
[ jeen
]
|
|
Change by Jeen Broekstra [18/Sep/12 01:32 AM]
|
|
Fix Version/s
|
|
2.6.10
[ 10760
]
|
|
Fix Version/s
|
2.7.0
[ 10630
]
|
|
|
Change by Jeen Broekstra [18/Sep/12 01:33 AM]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|
|
Bug
Resolved
Trivial
Sesame workbench Contexts screen can fail to show contexts due to caching