| Summary: | MSSQL: Unable to populate JBPM_ID_... tables | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Martin Vecera <mvecera> |
| Component: | JBossESB | Assignee: | Martin Vecera <mvecera> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.2 CP01 | CC: | max.andersen |
| Target Milestone: | --- | ||
| Target Release: | 4.2 CP02 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-545 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-10 09:29:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Martin Vecera
2008-05-14 12:56:31 UTC
Link: Added: This issue depends JBESB-1722 These files are generated by hibernate, on behalf of jBPM. They should be copied across to the SOA build from jBPM. This needs to be looked at by someone on the jBPM team. can someone make this a bit more explicit ? do you need to know where the database table schema is located ? the xml to load the identities in the db ? something else ? The real issue appears to be the pre-population of some of the jBPM tables. From what I can tell this data is example data, do we really need this? If it is not required then we can just remove the initialiser mbean. Sorry, the last suggestion should have been to remove the import.sql from the mbean. i don't know if you need it :-) jbpm on itself doesn't require the tables, nor the population of the tables. as the identity component in jbpm is pluggable as far as i can anticipate, you might need it to run the examples out of the box. depending on which examples that you have put in there. if the examples that are included in soa-p include assignment expressions, then there is a dependency on the pre-populated data. There are no jBPM examples shipped within the ESB/SOA Platform so, I assume, you are saying it is safe to remove this :) We are shipping the identity component however ;) It looks like it is safe to remove the import.sql from the build, we will do this and see what breaks. No examples? ls jboss-soa-p.4.2.0/jbpm-jpdl/examples/ action/ door/ mail/ readme.html rulesActionHandler/ simple/ variable/ customTaskInstance/ example.base.build.xml META-INF/ ruleFlow/ rulesAssignmentHandler/ task/ websale/ Hmmm, okay. I was under the impression that Trev was just overriding our jBPM files, I hadn't realised that jbpm-jpdl was also being shipped outside of the AS. The examples have no bearing on the ESB so we will continue to remove the import.sql configuration from our codebase. If the examples are to be supported then we will need to make sure that any accompanying documentation tells the user how to correctly configure the database. I suggest we create two sub tasks for this 1 - ESB team to remove the import.sql 2 - someone else to check the jBPM shipped externally to make sure it is correct (jBPM team???) The top level jbpm-jpdl was added for Developer studio, if they don't use the examples then are they needed? We will continue with the first part, removing import.sql. If the examples are needed then someone needs to do the second part. asked Max if developer studio uses these examples It was added because Koen said the distro was needed for the jbpm plugin to function properly. But why are the examples hurting SOA-P ? The examples aren't however the pre-population of the data for the examples is hurting us. The script being used to populate the example data does not work on all DB platforms. It should not be executed by default, only when someone is using those examples. I still don't understand what exactly is the "hurting part" here ? The examples are not meant to be preloaded until they are actually executed, correct? Precisely, which is why they are being removed. They should never have been included in our scripts in the first place. I should clarify my last and say that the 'pre-population of their data' is being removed and not that the examples are being removed. Verified in CR1 Link: Added: This issue relates to SOA-3031 |