Bug 973204
Summary: | ksession name is invisible in kmodule.xml on Project Screen and cannot be named default | ||
---|---|---|---|
Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Jiri Svitak <jsvitak> |
Component: | Business Central | Assignee: | Toni Rikkola <trikkola> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Marek Baluch <mbaluch> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 | CC: | mbaluch, rrajasek, zkrejcov |
Target Milestone: | DR5 | ||
Target Release: | 6.0.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-06 20:16:04 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: | |
Embargoed: |
Description
Jiri Svitak
2013-06-11 13:04:56 UTC
A part of the problem is that the ksession element is added into the kbase element, therefore, if you are creating a new ksession via the GUI, you need to select a kbase first. This way, the dialog for adding a ksession will close. If you don't select a kbase first, it won't. The GUI allows you to add ksession outside of a kbase it seems, which makes things quite buggy, as Jiri described above. Names don't seem to be exactly forbidden, but if you try to add a ksession outside of a kbase with the same name as an already existing kbase, you will get something like the following in your Problems tab: kmodulet.xml found, but unable to read org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 83; cvc-id.2: There are multiple occurrences of ID value 'default'. I'm not the responsible for that screen, Toni Rikkola or Michael Anstis should review this issue. Hi Mauricio, you are the default Assignee for business central component. Default assignee should be the one who is either able to fix the bug or who can reassign the bug to someone who does the fix. Also please change the status of the bug to modified only when it is fixed, not in the case that you think that it should be fixed by someone else. Thanks. p.s. Changing the assignee to Kris, so he can decide who will work on this issue. Verified on DR6 (Beta 5). Step 1) is not fixed but I will create a separate issue for it so we can better track it. This BZ has been part of the 6.0.0 stream. |