October 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-294) Revert drools event processor workaround due to aether dependency

by Gary Brown (JIRA)

Gary Brown created RTGOV-294: -------------------------------- Summary: Revert drools event processor workaround due to aether dependency Key: RTGOV-294 URL: https://issues.jboss.org/browse/RTGOV-294 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Revert the change that was made in RTGOV-271, to overcome the aether class not found issue. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-293) Deserialization issue when using clustered switchyard demo

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-293?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-293: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> made a comment on [bug 1014496|https://bugzilla.redhat.com/show_bug.cgi?id=1014496] Was also able reproduce using the remote-invoker quickstart in swyd 1.1.M4. However when testing fix in swyd 1.1.M4, got the following exception in the client: [INFO] --- exec-maven-plugin:1.2.1:java (default-cli) @ switchyard-quickstart-demo-cluster-client --- Oops ... something bad happened. org.switchyard.HandlerException: org.switchyard.SwitchYardException: SWITCHYARD010813: Cannot convert from 'org.switchyard.quickstarts.demo.cluster.Offer' to 'org.switchyard.quickstarts.demo.cluster.Application'. No registered Transformer available for transforming from 'java:org.switchyard.quickstarts.demo.cluster.Offer' to 'java:org.switchyard.quickstarts.demo.cluster.Application'. A Transformer must be registered. > Deserialization issue when using clustered switchyard demo > ---------------------------------------------------------- > > Key: RTGOV-293 > URL: https://issues.jboss.org/browse/RTGOV-293 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Activity request event is stored in the switchyard exchange properties so that it can be accessed when processing the response's activity event. > When using the clustered example, the exchange is serialized to be passed between clustered nodes. The receiving node does not have access to the activity model, thus causing class not found exceptions. > Keith suggests marking the property as transient to prevent it being serialized - but this still retains the property in the requestor, which should enable the activity event processing to function correctly. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-293) Deserialization issue when using clustered switchyard demo

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-293?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-293: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 1014496|https://bugzilla.redhat.com/show_bug.cgi?id=1014496] from NEW to MODIFIED > Deserialization issue when using clustered switchyard demo > ---------------------------------------------------------- > > Key: RTGOV-293 > URL: https://issues.jboss.org/browse/RTGOV-293 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Activity request event is stored in the switchyard exchange properties so that it can be accessed when processing the response's activity event. > When using the clustered example, the exchange is serialized to be passed between clustered nodes. The receiving node does not have access to the activity model, thus causing class not found exceptions. > Keith suggests marking the property as transient to prevent it being serialized - but this still retains the property in the requestor, which should enable the activity event processing to function correctly. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-293) Deserialization issue when using clustered switchyard demo

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-293?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-293: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1014496 > Deserialization issue when using clustered switchyard demo > ---------------------------------------------------------- > > Key: RTGOV-293 > URL: https://issues.jboss.org/browse/RTGOV-293 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Activity request event is stored in the switchyard exchange properties so that it can be accessed when processing the response's activity event. > When using the clustered example, the exchange is serialized to be passed between clustered nodes. The receiving node does not have access to the activity model, thus causing class not found exceptions. > Keith suggests marking the property as transient to prevent it being serialized - but this still retains the property in the requestor, which should enable the activity event processing to function correctly. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-293) Deserialization issue when using clustered switchyard demo

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-293?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-293. ------------------------------ Resolution: Done > Deserialization issue when using clustered switchyard demo > ---------------------------------------------------------- > > Key: RTGOV-293 > URL: https://issues.jboss.org/browse/RTGOV-293 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Activity request event is stored in the switchyard exchange properties so that it can be accessed when processing the response's activity event. > When using the clustered example, the exchange is serialized to be passed between clustered nodes. The receiving node does not have access to the activity model, thus causing class not found exceptions. > Keith suggests marking the property as transient to prevent it being serialized - but this still retains the property in the requestor, which should enable the activity event processing to function correctly. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-293) Deserialization issue when using clustered switchyard demo

by Gary Brown (JIRA)

Gary Brown created RTGOV-293: -------------------------------- Summary: Deserialization issue when using clustered switchyard demo Key: RTGOV-293 URL: https://issues.jboss.org/browse/RTGOV-293 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Activity request event is stored in the switchyard exchange properties so that it can be accessed when processing the response's activity event. When using the clustered example, the exchange is serialized to be passed between clustered nodes. The receiving node does not have access to the activity model, thus causing class not found exceptions. Keith suggests marking the property as transient to prevent it being serialized - but this still retains the property in the requestor, which should enable the activity event processing to function correctly. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-170) Atom feeds do not work very well in exisiting clients

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-170?page=com.atlassian.jira.plugin.... ] Work on SRAMP-170 stopped by Kurt Stam. > Atom feeds do not work very well in exisiting clients > ----------------------------------------------------- > > Key: SRAMP-170 > URL: https://issues.jboss.org/browse/SRAMP-170 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Atom Binding > Affects Versions: 0.1.1 - Workflow Demo > Reporter: Kurt Stam > Assignee: Kurt Stam > Priority: Minor > Fix For: 0.3.1 - jBPM - bugfix 1 > > Attachments: Screen Shot 2013-03-10 at 12.08.22 PM.png > > > When using exiting atom clients our feed don't work very well. I think one should be able to follow links down into an entry for example, but the link is not populated. We should investigate why this is. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-248) Maven mutliproject upload should recognize archive type

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-248?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-248. --------------------------- > Maven mutliproject upload should recognize archive type > ------------------------------------------------------- > > Key: SRAMP-248 > URL: https://issues.jboss.org/browse/SRAMP-248 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > It should be possible to just specify the distribution url; without having to specify the Type in the URL. The expanders can ship with hints regarding certain files in the archive representing a certain type of Type. i.e. switchyard.xml -> SwitchYardApplication. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-248) Maven mutliproject upload should recognize archive type

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-248?page=com.atlassian.jira.plugin.... ] Kurt Stam resolved SRAMP-248. ----------------------------- Resolution: Done > Maven mutliproject upload should recognize archive type > ------------------------------------------------------- > > Key: SRAMP-248 > URL: https://issues.jboss.org/browse/SRAMP-248 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > It should be possible to just specify the distribution url; without having to specify the Type in the URL. The expanders can ship with hints regarding certain files in the archive representing a certain type of Type. i.e. switchyard.xml -> SwitchYardApplication. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-243) Fix KieExpander

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-243?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-243. --------------------------- > Fix KieExpander > --------------- > > Key: SRAMP-243 > URL: https://issues.jboss.org/browse/SRAMP-243 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > Should set the right model type for BPMN and DRL files. -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2013