Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Won't Fix
-
Affects Version/s: 1.2.0
-
Fix Version/s: 1.3.3
-
Component/s: Petals Tools
-
Security Level: Public
-
- Environment:
- All.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Vincent Zurczak [ vzurczak ] |
| Summary | Create a default component in the SU wizard | Extend the SU wizard from the preferences |
| Priority | Blocker [ 1 ] | |
| Description |
Some components are not supported in the studio. That's a fact.
Sometimes, you also develop your own component. There should be a default wizard to create a custom service-unit, with a basic jbi.xml file. |
Some components are not supported in the studio. That's a fact.
Sometimes, you also develop your own component. It would be great to be able to register a new kind of Petals component through preferences. The preferences should help to define: * A new version of a known component. ** Information required: is-provides, is-consumes, the directory of the XSD files for the wizard (optional). * A new component. ** Information required: the component name, the component kind (BC, SE), one or several use case categories and one or several versions (at least one is required). Updating these preferences should make these components visible in the SU wizard. With this solution, there is no possible customisation of the wizard. For more options, you need to create a plug-in. If there is no XSD file, then the wizard will have to create a default jbi.xml with incomplete mark-ups. |
| Affects Version/s | 1.2.0 [ 10079 ] | |
| Affects Version/s | 1.2.0-RC1 [ 10250 ] |
| Resolution | Won't Fix [ 2 ] | |
| Status | New [ 10000 ] | Resolved [ 10004 ] |
| Status | Resolved [ 10004 ] | Closed [ 10005 ] |
| Fix Version/s | 1.3.3 [ 10367 ] |