[
https://issues.apache.org/jira/browse/ARIES-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bartosz Kowalewski updated ARIES-313:
-------------------------------------
Attachment: aries-313.diff
Attaching a patch. In summary it:
- Moves the JDBC version of the blog sample to an in-memory DB and tells
Derby to create this DB (the JPA version is not moved to the in-memory
DB, but I think that this change should also take place)
- Adds a simple itest (based on Zoe's JPA one) that tests the jdbc
version of this sample
- Modifies the BlogPersistenceServiceImpl class, so that it setups all
the required tables through an init-method and drops them on shutdown.
The latter is not really required as this is an in-memory DB :). This
code needs clean-up and it's extremely simple.
Similarly to what is for example done in ActveMQ when setting up the
underlying DB, it uses hardcoded SQL statements. It even does not
check if these tables are already there. It assumes that it's not
possible that those tables are in place as an embedded DB is used.
> The samples should all have tests!
> ----------------------------------
>
> Key: ARIES-313
> URL: https://issues.apache.org/jira/browse/ARIES-313
> Project: Aries
> Issue Type: Improvement
> Components: Samples
> Reporter: zoe slattery
> Assignee: zoe slattery
> Attachments: aries-313.diff
>
>
> Someone on the user mailing list reported that the blog sample wasn't
> working. It wasn't because we had made changes to the bundles and because
> there are no tests for the blog sample the only way to see that it was broken
> was by checking running it. We really need tests for the 'show case' samples
> to make sure that when ever a user tries to run them they just work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
