12:42 p.m.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to
currently open any associated editor manually to edit particular files, such as
jboss-smooks.xml from the SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
5:52 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich commented on JBIDE-5191:
----------------------------------------------
Brian, I have committed implementation for the SmooksAction case (assuming, as in
selector, that path in smooksConfig is relative to esb content folder). Any linking is
possible, please attach a list of cases. There is a limitation, though, it is easy to
assign selector and link for an attribute of a predefined action, and not so easy to guess
what a generic attribute of a generic action may be. Will you then please attach also a
complete list of predefined actions which are not implemented yet in the editor?
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
10:08 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
Awesome. That works great Slava.
Others we'd like to have done...
org.jboss.soa.esb.actions.converters.SmooksTransformer - the Resource Config property
references a smooks configuration. Could we also add a Browse button to select the smooks
config file?
org.jboss.soa.esb.actions.scripting.GroovyActionProcessor - the Script property references
a groovy script (for example - /scripts/ActionXProcessor.groovy). If the Groovy editor was
added by the end-user, it would be nice to open it. Could we also add a Browse button?
org.jboss.soa.esb.actions.ContentBasedRouter - the Rule Set property references a Drools
file (MyESBRules-XPath.drl) and the Rule Language property references a DSL file
(XPathLanguage.dsl). Again, Browse buttons for these two files would be helpful.
There may be others, but they will require some additional actions to be added for ESB 4.7
and I'll open a separate JIRA for that once I work out the details.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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:05 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
I've added https://jira.jboss.org/jira/browse/JBIDE-5199 as a related issue to add
some new functionality for ESB 4.7. the XsltAction class would need to open the associated
template file in the XSLT editor (/Proxy_Versioning_RequestTransform.xsl).
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
5:54 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
This info is from Burr:
just for clarity sake:
Groovy
<action name="setup_key"
class="org.jboss.soa.esb.actions.scripting.GroovyActionProcessor">
<property name="script"
value="/scripts/setup_key.groovy" /> <!-- this
should open in Groovy editor -->
</action>
jBPM
<action name="start_a_new_order_process"
class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor">
<property name="command"
value="StartProcessInstanceCommand" />
<property name="process-definition-name"
value="bpm4_ESBOrderProcess" />
<property name="key" value="body.businessKey"
/>
<property name="esbToBpmVars">
<mapping esb="BODY_CONTENT"
bpm="entireOrderAsXML" />
</property>
</action>
Drools
<action
class="org.jboss.soa.esb.actions.BusinessRulesProcessor"
name="BRP">
<property name="ruleSet"
value="Priority_Rules.drl" /> <!-- this should
open in Drools editor -->
<property name="ruleReload" value="true" />
<property name="object-paths">
<object-path esb="body.orderHeader" />
<object-path esb="body.customer" />
</property>
</action>
Drools based CBR
<action
class="org.jboss.soa.esb.actions.ContentBasedRouter"
name="ContentBasedRouter">
<property name="ruleSet" value="CBRRules.drl"
/> <!-- this should open in Drools editor -->
<property name="ruleReload" value="true" />
<property name="destinations">
<route-to
destination-name="SuperSpecialCustomerService"
service-category="ConciergeManager"
service-name="ConciergeService" />
<route-to
destination-name="SpecialCustomerService"
service-category="DistributionManager"
service-name="DistributionService" />
<route-to
destination-name="RegularCustomerService"
service-category="BasicShipping"
service-name="ShipperService" />
</property>
<property name="object-paths">
<object-path esb="body.orderHeader" />
<object-path esb="body.customer" />
</property>
</action>
XPath based CBR
<action
class="org.jboss.soa.esb.actions.ContentBasedRouter"
name="ContentBasedRouter">
<property name="cbrAlias" value="XPath"/>
<property name="destinations">
<namespace prefix="ord"
uri="http://org.jboss.soa.esb/Order" />
<route-to service-category="BlueTeam"
service-name="GoBlue"
expression="/ord:Order[@statusCode='0']" />
<route-to service-category="RedTeam"
service-name="GoRed"
expression="/ord:Order[@statusCode='1']" />
<route-to service-category="GreenTeam"
service-name="GoGreen"
expression="/ord:Order[@statusCode='2']" />
</property>
</action>
XSLTAction
<action name="proxy-transform-old-to-new"
class="org.jboss.soa.esb.actions.transformation.xslt.XsltAction">
<property name="templateFile"
value="/Proxy_Versioning_RequestTransform.xsl"/> <!-- this should open in
XSLT editor -->
<property name="failOnWarning"
value="true"/>
<property name="resultType"
value="STRING"/>
</action>
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
4:04 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich commented on JBIDE-5191:
----------------------------------------------
Brian, thank you for the details. Some more questions.
Are paths "/scripts/setup_key.groovy", "Priority_Rules.drl",
"CBRRules.drl", "/Proxy_Versioning_RequestTransform.xsl" given
relative to esb content folder?
Which value should be opened in jBPM and XPath cases, and what is the search algorithm?
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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:47 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
Questions are good. I'm asking about the paths to the Groovy, Drools, and XSL file and
if they're relative to the ESB content folder now.
I'm not sure I understand your second question. When you say "which value"
what are you referring to? and the same for the "search algorithm"?
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
5:01 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich commented on JBIDE-5191:
----------------------------------------------
In other cases there is a comment <!-- this should open in ... editor --> near
element/attribute with value to be opened, it is missing in jBPM and XPath cases.
'Search algorithm' is intuitive in other cases - take esb content folder and
append to its path the attribute value to obtain the path of the resource in question,
while it is not obvious to me what to do in jBPM and XPath cases.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
8:58 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
Right. Sorry about that. Didn't mean to confuse the issue. I'd let those go for
now. I don't have a clear understanding of what would be necessary to open them
either.
According to Kevin Conner (ESB) as to the paths of the Groovy, Drools, and XSL files -
"They should all be taken as resources, so relative to the root of the esb deployment
or contained within a jar file"
So just treat them like you did the Smooks one and I think we should be good.
Thanks!
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
9:42 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-5191:
-------------------------------------
Hi again...
I gained some additional information from Kevin Conner about the
org.jboss.soa.esb.actions.ContentBasedRouter action...
Looks like there's a couple of different flavors of this action.
One is the Drools version you've already seen... If cbrAlias is not present or maps to
"JBRules" or "Drools" (case insensitive) then it is the
JBossRulesRouter. So in this case, the "ruleSet" contains the path to a Drools
file, and should open the Drools editor.
The other one is the XPath version... If cbrAlias is "XPath" then it is the
XPathRouter, which it looks like you can use a properties file to define the XPath
routing... I'll append the info from Kevin below... If it's one of these xpath
properties files, it looks like we should simply open the file in a text editor.
On 18/11/09 11:55, Kevin Conner wrote:
<property name="ruleSet"
value="/org/jboss/soa/esb/actions/cbr/xpath/rules.properties"/>
The contents of this file is a normal property file containing the rules.
scat-blue=/order/header[@cat='blue']
scat-red=/order/header[@cat='red']
scat-green=/order/header[@cat='green']
The format of that file is
<destination>=<expression>
where destination defaults to category-name (the issue I thought we had)
and the destination is retrieved from the destinations. You can specify
a proper destination though, and should do.
So a proper config would look like the following.
<action class="org.jboss.soa.esb.actions.ContentBasedRouter"
name="ContentBasedRouter">
<property name="cbrAlias" value="XPath"/>
<property name="ruleSet" value="/xpathRuleSet"/>
<property name="destinations">
<namespace prefix="ord" uri="http://org.jboss.soa.esb/Order"
/>
<route-to service-category="BlueTeam" service-name="GoBlue"
destination-name="blue" />
<route-to service-category="RedTeam" service-name="GoRed"
destination-name="red" />
<route-to service-category="GreenTeam" service-name="GoGreen"
destination-name="green" />
</property>
</action>
and the contents of the xpathRuleSet resource would be something like
the following
blue=/ord:Order[@statusCode='0']
red=/ord:Order[@statusCode='1']
green=/ord:Order[@statusCode='2']
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
10:55 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich commented on JBIDE-5191:
----------------------------------------------
Brian, I implemented these cases, only for routers, selector is made common it always
contains both drl and properties files, is it ok? I also tried to add to selector Java
source folders and jars, please look at new selector.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
4:04 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-5191:
-------------------------------------
Hi Slava...
I tried it with a *.properties file and a *.drl file and it opens fine with the
*.properties file, but not for the *.drl file and I don't see my *.drl file in the
browse dialog either. Is it looking for both extensions?
Can you give me an idea of where to look for the Java source folder/jars selector?
--Fitz
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
4:35 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich updated JBIDE-5191:
-----------------------------------------
Attachment: new-resource-selector.jpg
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
5:04 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich commented on JBIDE-5191:
----------------------------------------------
Brian, please look at new-resource-selector.jpg. It is just the improved browse dialog.
Called for 'rule set' on Content Based Router, it collects both drl and properties
files. Besides esb content folder, it contains also Java src folders and jar folders.
Maybe, you have tested a build that still misses my contribution and could not have seen
my changes yet.
If with relevant build, drl file is not still open, please check for exceptions and if
possible, attach the example project.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
10:15 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
I discovered the problem this morning. If I have the ESB editor open and browse for the
ContentBasedRouter file for the Rule Set property, it populates just fine. The issue is
when you browse once, then add a new *.properties or *.drools file to the project, and
browse again. It appears to not be refreshing the list based on workspace changes.
Can you look at that to see if we can do something about the caching and re-caching if
there are changes to the project or workspace?
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich commented on JBIDE-5191:
----------------------------------------------
The internal model of the project is listening to workspace and updates, but it takes
time; the update is going as a background job. Please make sure that after several
modifications to project and check if at least some of changes are picked up yet.
I will try to check before each start of browser/content assist if update job is waiting
and when so then force update.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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:12 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich commented on JBIDE-5191:
----------------------------------------------
By the way, which extension is correct: drl or drools or both?
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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:14 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
How much time does it typically take? What kind of schedule is it on?
And forcing an update when the browser/content assist is used would be a great solution to
this problem.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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:14 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
"drl" is correct. I mistyped in my previous comment. Sorry for the confusion.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
6:11 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5191:
--------------------------------------------
slava, eclipse Open resource picks up new files (almost) instantly - are we using some
other model for this ?
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
8:56 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich commented on JBIDE-5191:
----------------------------------------------
We use xmodel that provides for browser, content assist and open action in a common way.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
12:02 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Viacheslav Kabanovich resolved JBIDE-5191.
------------------------------------------
Resolution: Done
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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:15 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5191:
------------------------------------------
Thanks for the great work on this Slava. Appreciate the help!
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
4:24 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-5191:
-------------------------------------
Attachment: ESB.Example.XML2POJO2.zip
Max, here's an example project that takes advantage of a couple of linked files...
If you drill into the Service's actions list, you'll see a number of actions.
Three of these link to other editors:
1) displayBeforeTransformer links to the action class (click on "Class:" which
is underlined)
2) discover-message-origin links to a groovy script (click on "Script:" which is
underlined) - if the Groovy editor is installed it will open in it, otherwise it just
opens it as a text file
3) transform links to a Smooks config (click on "Smooks Config:" which is
underlined) and opens in the Smooks Configuration editor
There are also some new actions in JBIDE-5199 that should be added, but we're waiting
on info from Kevin Conner. I've asked Slava to add the XsltAction, which is one we
know is new.
ESB Editor - linking in other editors where appropriate
-------------------------------------------------------
Key: JBIDE-5191
URL: https://jira.jboss.org/jira/browse/JBIDE-5191
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.M4
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Fix For: 3.1.0.CR1
Attachments: ESB.Example.XML2POJO2.zip, new-resource-selector.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
New JIRA to deal with requirement "Developer Tools: Linking Editors" in the
SOA-P PRD.
From the ESB editor, depending on the action used, the user has to currently open any
associated editor manually to edit particular files, such as jboss-smooks.xml from the
SmooksAction. This is a usability hit.
It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the
field for the file would show up as a hyperlink that the user could click to open the file
in the associated editor. So in the SmooksAction case, the "Smooks Config:"
label would become a hyperlink that would open the Smooks editor for the file referenced
in the field.
Product management is looking to link:
Smooks editor
Drools editor
jPDL editor
XSLT editor (once it gets added)
Groovy editor (if added by the end-user)
Would this be possible for JBDS 3?
--
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
5972
days inactive
5991
days old
jbosstools-issues@lists.jboss.org
23 comments
3 participants
participants (3)
-
Brian Fitzpatrick (JIRA) -
Max Rydahl Andersen (JIRA)
-
Viacheslav Kabanovich (JIRA)