[JBoss JIRA] Created: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
10:53 a.m.
Extend ESB Editor to support some important objects presented in XML with "free
content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12407596 ]
Burr Sutter commented on JBIDE-2022:
------------------------------------
Ideally the ESB Editor would be aware of all "out of the box" actions. See
http://jira.jboss.com/jira/browse/JBIDE-2023
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12407597 ]
Burr Sutter commented on JBIDE-2022:
------------------------------------
The real tricky part will be the fact that each Actions configuration is unique and NOT
prescribed in a java interface. My only suggestion is that you have the ESB team
produce a template XML config, per action that the tool can use a template for the
end-user.
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:27 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12408098 ]
Viacheslav Kabanovich commented on JBIDE-2022:
----------------------------------------------
"Message Action Guide" contains description and templates for "out of the
box" actions.
All of them can be implemented in ESB editor, with their own creation wizards and edit
forms.
Class name for each of these actions will be preset and non-editable, properties described
in the guide will be
recognized to have specific field editors; although I think it will be reasonable to
preserve opportunity to add generic properties as well (so that changes to action behavior
in next ESB versions would not knock down the editor).
In approximate estimation that work may take from 7 to 10 days.
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:42 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Max Andersen updated JBIDE-2022:
--------------------------------
Fix Version/s: 2.2.x
ok for 2.2.
Slava, I suggest you take one of these examples you found and implement and get feedback
on that one, instead of doing the whole set without feedback.
Burr, any single or small set of the predefined actions that would be most interesting use
as a guineypig ?
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 2.2.x
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:14 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12409852 ]
Mark Little commented on JBIDE-2022:
------------------------------------
Easier to start with some of the converter actions, e.g., ObjectInvoke or
ObjectToCSVString. They are simple enough.
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 2.2.x
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:24 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Attachment: menu_Add_Pre-Packed_Action.jpg
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: menu_Add_Pre-Packed_Action.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:36 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12416434 ]
Max Rydahl Andersen commented on JBIDE-2022:
--------------------------------------------
Why the two level deep context menu ?
Should Add Action.. just be e.g. Add generic action... under New... together with the
"pre-packed" action ? (pre-packed is not a good term either ;)
That would give you less nesting.
These selections also should be available in the Add Action... menu in the form editor
where I think most users would click instead of using the conext menu.
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: menu_Add_Pre-Packed_Action.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:42 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: Edit_Form_for_Content_Based_Router.jpg
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Content_Based_Router.jpg,
menu_Add_Pre-Packed_Action.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:44 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: (was: Edit_Form_for_Content_Based_Router.jpg)
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: menu_Add_Pre-Packed_Action.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:46 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: Edit_Form_for_Conten_Based_Router.jpg
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg,
menu_Add_Pre-Packed_Action.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:02 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12416442 ]
Viacheslav Kabanovich commented on JBIDE-2022:
----------------------------------------------
There are now 18 pre-packed actions, and in future more can be added. I think menu should
not be unlimitedly long, but ok, I have just tried to have 18 in one list and it looks
good.
I Agree that 'Add generic action...' sounds better.
I borrowed term 'pre-packed' from JBossESB 4.2.1 GA Message Action Guide.
"available in the Add Action... menu in the form editor" - done.
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg,
menu_Add_Pre-Packed_Action.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:07 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: (was: menu_Add_Pre-Packed_Action.jpg)
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:09 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: menu_New_Action_in_form.jpg
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_form.jpg,
menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:09 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: menu_New_Action_in_tree.jpg
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_form.jpg,
menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:31 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12416446 ]
Max Rydahl Andersen commented on JBIDE-2022:
--------------------------------------------
ok, good that the form editor has these too.
About the menu I did not make my self clear.
For the context menu it should be:
New ... > Add Action > (the long menu with "Add Generic action.." as one
of the options)
That removes a level of the context menu.
From the form menu it would be
Add Action > (the long menu with "Add Generic action.." as one of the
options)
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_form.jpg,
menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: (was: menu_New_Action_in_form.jpg)
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: menu_New_Action_in_tree.jpg
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: (was: menu_New_Action_in_tree.jpg)
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:58 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich updated JBIDE-2022:
-----------------------------------------
Attachment: menu_New_Action_in_form.jpg
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_form.jpg,
menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:20 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12416452 ]
Max Rydahl Andersen commented on JBIDE-2022:
--------------------------------------------
much better, dont you think so to ? :)
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_form.jpg,
menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:59 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]
Viacheslav Kabanovich resolved JBIDE-2022.
------------------------------------------
Resolution: Done
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 3.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_form.jpg,
menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:18 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[
https://jira.jboss.org/jira/browse/JBIDE-2022?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-2022:
---------------------------------
Affects: [Documentation (Ref Guide, User Guide, etc.)]
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: https://jira.jboss.org/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.0.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_form.jpg,
menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:11 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
[
https://jira.jboss.org/jira/browse/JBIDE-2022?page=com.atlassian.jira.plu...
]
Anton Klimkovich closed JBIDE-2022.
-----------------------------------
JBossTools-3.0.0.CR1-N200811201326-ALL
Extend ESB Editor to support some important objects presented in XML
with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: https://jira.jboss.org/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.0.0.alpha
Attachments: Edit_Form_for_Conten_Based_Router.jpg, menu_New_Action_in_form.jpg,
menu_New_Action_in_tree.jpg
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a
small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5700
days inactive
5932
days old
jbosstools-issues@lists.jboss.org
23 comments
8 participants
participants (8)
-
Anonymous (JIRA) -
Anton Klimkovich (JIRA)
-
Burr Sutter (JIRA)
-
Denis Golovin (JIRA)
-
Mark Little (JIRA)
-
Max Andersen (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Viacheslav Kabanovich (JIRA)