[JBoss JIRA] (JBIDE-10406) JBoss BPEL Editor showing error message for valid Assign activity
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10406?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky closed JBIDE-10406.
-------------------------------------
Verified with JBTIS 4.1.2
> JBoss BPEL Editor showing error message for valid Assign activity
> -----------------------------------------------------------------
>
> Key: JBIDE-10406
> URL: https://issues.jboss.org/browse/JBIDE-10406
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: bpel
> Reporter: Michael Pellegrini
> Assignee: Robert (Bob) Brodt
> Labels: bpel
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: Test.zip
>
>
> The assign activity is reporting an error, which only shows up in the Project Explorer view (not in the actual editor). The assign is a sample assign between two variables. The error is:
> The XPath segment "child::app:Application" cannot be resolved. Test.bpel /Test/bpelContent line 45 BPEL Validation Marker
> Although it shows as an error, it actually deploys and runs fine.
> Have a sample project attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-10406) JBoss BPEL Editor showing error message for valid Assign activity
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10406?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky resolved JBIDE-10406.
---------------------------------------
Resolution: Done
Maybe Bob forgot to set this issue as resolved, but this error is not present from SOA tooling 3.3. Now, the message is marked as a warning
> JBoss BPEL Editor showing error message for valid Assign activity
> -----------------------------------------------------------------
>
> Key: JBIDE-10406
> URL: https://issues.jboss.org/browse/JBIDE-10406
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: bpel
> Reporter: Michael Pellegrini
> Assignee: Robert (Bob) Brodt
> Labels: bpel
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: Test.zip
>
>
> The assign activity is reporting an error, which only shows up in the Project Explorer view (not in the actual editor). The assign is a sample assign between two variables. The error is:
> The XPath segment "child::app:Application" cannot be resolved. Test.bpel /Test/bpelContent line 45 BPEL Validation Marker
> Although it shows as an error, it actually deploys and runs fine.
> Have a sample project attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-6010) Tooling Support for Byteman Rule Injection
by Andrew Dinn (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6010?page=com.atlassian.jira.plugin... ]
Andrew Dinn commented on JBIDE-6010:
------------------------------------
Hi Masao,
Thanks for offering to contribute your code. If you could provide us with your plugin sources we could take a look at them and see what we might be able to do to help integrate them into JBDS. Max Andersen may be able to schedule someone from the JBDS team to make this assessment. Max?
> Tooling Support for Byteman Rule Injection
> ------------------------------------------
>
> Key: JBIDE-6010
> URL: https://issues.jboss.org/browse/JBIDE-6010
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: z - Legacy - integration
> Reporter: Andrew Dinn
> Labels: integration
> Fix For: LATER
>
>
> It would be nice to have support for Byteman in these areas:
> 1) editor support for creation and modification of Byteman rule files
> 2) debugger support for detection of successful or ailed rule injection at runtime
> 3) debugger support for stepping through injected rule code
> the byteman agent already runs a listener which provides the info required for ii.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-14921) In BPEL editor design mode and source mode differs
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14921?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-14921:
--------------------------------------
Fix Version/s: 4.0.0.Alpha1-SOA
(was: 3.3.3.Final-SOA)
> In BPEL editor design mode and source mode differs
> --------------------------------------------------
>
> Key: JBIDE-14921
> URL: https://issues.jboss.org/browse/JBIDE-14921
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: bpel, integration-platform
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: Salutations.zip
>
>
> In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like
> If
> -> Else
> -> ElseIf
> By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows
> If
> -> ElseIf
> -> Else
> but the source includes the previous oder.
> This can be confusing since the editor shows something which looks good but in fact it is not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-14921) In BPEL editor design mode and source mode differs
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14921?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky closed JBIDE-14921.
-------------------------------------
Verified with JBTIS 4.1.2. Note that old SOA tooling for JBT 3.3 doesn't contain this fix. This fix is SOA toolign for JBT 4 and higher which is now called JBTIS (JBDSIS).
> In BPEL editor design mode and source mode differs
> --------------------------------------------------
>
> Key: JBIDE-14921
> URL: https://issues.jboss.org/browse/JBIDE-14921
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: bpel, integration-platform
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: Salutations.zip
>
>
> In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like
> If
> -> Else
> -> ElseIf
> By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows
> If
> -> ElseIf
> -> Else
> but the source includes the previous oder.
> This can be confusing since the editor shows something which looks good but in fact it is not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months