Github user bwmcbride commented on the pull request:
https://github.com/apache/jena/pull/123#issuecomment-177595681
Thanks for the steer. So fix in Builder.buildDataService.
The simple thing to do to just solve the problem for two services in the
server configuration file is to create a static memoizing map in the Builder
class.
One of the calls to Builder.buildDataAccessPoint, which calls
Builder.buildDataService is from ActionDatasets.execPostContainer. That seems
to be taking an HTTP POST, interpreting it as a configuration and then creating
a service corresponding to that configuration. There appears also to be a
DELETE operation.
So, in the case of the sequence:
- POST config for service A
- DELETE service A
- POST different config for service A
the dataset created for the first POST will get reused.
Is it ok to use a simple static map in the Builder class as 'a start'?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
