November 2008 - overlord-issues - Jboss List Archives

[JBoss JIRA] Updated: (SOAG-39) Changes to error highlighting when displaying jboss-esb.xml error in XML editor

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-39?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-39: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) Affects Version/s: 1.0 MR1 (was: 1.0 CR1) > Changes to error highlighting when displaying jboss-esb.xml error in XML editor > ------------------------------------------------------------------------------- > > Key: SOAG-39 > URL: https://jira.jboss.org/jira/browse/SOAG-39 > Project: SOA Governance > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 1.0 MR1 > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0 MR1 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Currently an error on an action or property in the action results in the complete Action being highlighted as an error. > Suggestion is to just highlight the first line of the Action, if the error is related to the complete action, or highlight the property within the action if property related. > However, if a graphical editor is being used to show the ESB config, then focusing on the complete action (i.e. graphical component) may be all that is possible, as Eclipse does not provide default behaviour for focusing on individual properties. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-38) Detect change to dependent Java classes, to cause jboss-esb.xml to be re-validated.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-38?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-38: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) Affects Version/s: 1.0 MR1 (was: 1.0 CR1) > Detect change to dependent Java classes, to cause jboss-esb.xml to be re-validated. > ----------------------------------------------------------------------------------- > > Key: SOAG-38 > URL: https://jira.jboss.org/jira/browse/SOAG-38 > Project: SOA Governance > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 1.0 MR1 > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0 MR1 > > > Currently if a Java class referenced in the 'session' property is modified, it does not result in the jboss-esb.xml being revalidated. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-45) Updates of 'MessageRouterAction'

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-45?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-45: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) Affects Version/s: 1.0 MR1 (was: 1.0 CR1) > Updates of 'MessageRouterAction' > -------------------------------- > > Key: SOAG-45 > URL: https://jira.jboss.org/jira/browse/SOAG-45 > Project: SOA Governance > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Affects Versions: 1.0 MR1 > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 MR1 > > > 1. Currently the 'identities' elements are contained at the same level as the 'message' elements - however the set of identities will be specific to the message type > 2. The 'serviceDescriptionName' attribute should be a property on the MessageRouterAction, as opposed to an attribute on the 'route' element, as it will be the same across all routes. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-44) Tool's plugin should be only validated against conversation actions.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-44?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-44: ------------------------ Component/s: Tooling Fix Version/s: 1.0 MR1 (was: 1.0 CR1) Affects Version/s: 1.0 MR1 (was: 1.0 CR1) > Tool's plugin should be only validated against conversation actions. > -------------------------------------------------------------------- > > Key: SOAG-44 > URL: https://jira.jboss.org/jira/browse/SOAG-44 > Project: SOA Governance > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 1.0 MR1 > Reporter: Jeff Yu > Assignee: Gary Brown > Fix For: 1.0 MR1 > > Attachments: error.png, jboss-esb.xml > > > Right now, the tool is also validating jboss-esb.xml that doesn't contain the conversation based action. The validation should be only performed for conversation based action. > Step to reproduce: > --------------------------------- > Download the JBossESB code, and then import it to the eclipse. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-34) Add example scenario description in README.txt

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-34?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-34: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) > Add example scenario description in README.txt > ---------------------------------------------- > > Key: SOAG-34 > URL: https://jira.jboss.org/jira/browse/SOAG-34 > Project: SOA Governance > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 MR1 > > > Add example scenario description in README.txt -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-32) Updating the 'decision-method' to 'expression' name globally for conversation actions.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-32?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-32: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) > Updating the 'decision-method' to 'expression' name globally for conversation actions. > -------------------------------------------------------------------------------------- > > Key: SOAG-32 > URL: https://jira.jboss.org/jira/browse/SOAG-32 > Project: SOA Governance > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 MR1 > > > Updating the 'decision-method' to 'expression' name globally for conversation actions. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-37) Change 'response....' property names to 'return....' on PerformAction

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-37?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-37: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) Affects Version/s: 1.0 MR1 (was: 1.0 CR1) > Change 'response....' property names to 'return....' on PerformAction > --------------------------------------------------------------------- > > Key: SOAG-37 > URL: https://jira.jboss.org/jira/browse/SOAG-37 > Project: SOA Governance > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Affects Versions: 1.0 MR1 > Reporter: Gary Brown > Assignee: Jeff Yu > Fix For: 1.0 MR1 > > > Currently the optional service category and name specified on the PerformAction, to define the service descriptor to invoke when the performed sub-session has completed, is called 'responseServiceCategory' and 'responseServiceName'. > This implies there is a response being returned from the performed sub-session. > Would prefer the property names to be changed to 'returnServiceCategory' and 'returnServiceName'. > These have been updated in the tools. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-30) Control Action has the capability of having 'identity' properties.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-30?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-30: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) > Control Action has the capability of having 'identity' properties. > ------------------------------------------------------------------ > > Key: SOAG-30 > URL: https://jira.jboss.org/jira/browse/SOAG-30 > Project: SOA Governance > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 MR1 > > > For any control actions, it is able to have the 'identity' properties to retrieve the session, detail see the JBoss Forum Reference. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-29) Separate Supplier/Credit Agency service in its esb artifact.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-29?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-29: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) > Separate Supplier/Credit Agency service in its esb artifact. > ------------------------------------------------------------ > > Key: SOAG-29 > URL: https://jira.jboss.org/jira/browse/SOAG-29 > Project: SOA Governance > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 MR1 > > > Separating the Supplier/Credit Ageny service into its own artifact, otherwise, it will have too many services (more than 20), and it is better for reusing in the examples. say Broker and Purchase will use the same Credit Agency. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-27) Get hibernate.StaleStateException when run the example second time. (different identity)

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-27?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-27: ------------------------ Fix Version/s: 1.0 MR1 (was: 1.0 CR1) > Get hibernate.StaleStateException when run the example second time. (different identity) > ---------------------------------------------------------------------------------------- > > Key: SOAG-27 > URL: https://jira.jboss.org/jira/browse/SOAG-27 > Project: SOA Governance > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 MR1 > > > Reproduce steps: > 1) Run the purchase example as the README.txt described. > 2) Update the id value (say change it to 6) in the BuyerClient.java, and then run "ant runClient" again, > 3) You will see this error. > It seems it was caused by message resent by JMS??? > Exception: > ----------------- > org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1 > at org.hibernate.jdbc.Expectations$BasicExpectation.checkBatched(Expectations.java:61) > at org.hibernate.jdbc.Expectations$BasicExpectation.verifyOutcome(Expectations.java:46) > at org.hibernate.jdbc.BatchingBatcher.checkRowCounts(BatchingBatcher.java:68) > at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:237) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:146) > at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) > at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) > at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) > at org.jboss.soa.overlord.jbossesb.actions.ConversationAction.process(ConversationAction.java:204) > at sun.reflect.GeneratedMethodAccessor165.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) > at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) > at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) > at java.lang.Thread.run(Thread.java:595) > 21:47:01,503 INFO [ConversationAction] Session Key is [null] Body is: [<CreditCheckResponse id="6"></CreditCheckResponse>] > 21:47:01,428 INFO [ConversationAction] Session Key is [3] Body is: [<CreditCheckResponse id="6"></CreditCheckResponse>] > 21:47:01,639 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session > org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1 > at org.hibernate.jdbc.Expectations$BasicExpectation.checkBatched(Expectations.java:61) > at org.hibernate.jdbc.Expectations$BasicExpectation.verifyOutcome(Expectations.java:46) > at org.hibernate.jdbc.BatchingBatcher.checkRowCounts(BatchingBatcher.java:68) > at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:237) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:146) > at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) > at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) > at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) > at org.jboss.soa.overlord.jbossesb.actions.ConversationAction.process(ConversationAction.java:204) > at sun.reflect.GeneratedMethodAccessor165.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) > at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) > at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) > at java.lang.Thread.run(Thread.java:595) -- 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

16 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues November 2008