| Summary: | Creating Modeshape server in JBDS 4.0 beta1 - intermittent problem where error raised regarding existing user "admin" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> | ||||
| Component: | EDS | Assignee: | Van Halbert <vhalbert> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.1.0.ER3 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-2508 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
SOA-P 5.1 ER3 build
Version: 4.0.0.Beta1
Build id: v201010052359R
|
|||||
| Last Closed: | 2010-11-02 03:12:50 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: | |||||
| Attachments: |
|
||||||
|
Description
Len DiMaggio
2010-10-28 02:34:48 UTC
Attachment: Added: Screenshot-user-admin.png Link: Added: This issue depends MODE-988 Link: Added: This issue is a dependency of JBDS-1388 Investigate for 5.1.0, if they should be in SOA 5.1.0, Van will set the Fixed Version. The URL in the screen shot is wrong. It should not have the "repository" at the end of it. URLs should end in "modeshape-rest." With that said, it looks like you will get there error any time a ModeShape server is defined but can't be connected to. I think a good solution would be to only have servers that can be connected to show up in the publish dialog. According to the engineer, the problem seen is what is suppose to happen when a new modeshape server is trying to be created when it already exists. If there is a usability issue here, then there needs to be recommendations as to what should happen. |