February 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2320) XStreamToObject. Add support for implicit collections and field alias

by Misel Lukic (JIRA)

XStreamToObject. Add support for implicit collections and field alias --------------------------------------------------------------------- Key: JBESB-2320 URL: https://jira.jboss.org/jira/browse/JBESB-2320 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Misel Lukic Support for implicit collections and field aliases in the XStream action class, as in the APIs aliasField(String alias, Class definedIn, String fieldName) addImplicitCollection(Class ownerType, String fieldName, String itemFieldName, Class itemType) By specifying properties as "class-alias"? -- 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

17 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2336) Upgrade smooks to version 1.1.1

by Kevin Conner (JIRA)

Upgrade smooks to version 1.1.1 ------------------------------- Key: JBESB-2336 URL: https://jira.jboss.org/jira/browse/JBESB-2336 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Tom Fennelly Fix For: 4.5 -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2337) xml files for ESBContractGeneratorUnitTest contain extraneous characters

by Kevin Conner (JIRA)

xml files for ESBContractGeneratorUnitTest contain extraneous characters ------------------------------------------------------------------------ Key: JBESB-2337 URL: https://jira.jboss.org/jira/browse/JBESB-2337 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Trivial Fix For: 4.5 Doesn't change the test results, just tidying up -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2335) Fix ivy/smooks integration

by Kevin Conner (JIRA)

Fix ivy/smooks integration -------------------------- Key: JBESB-2335 URL: https://jira.jboss.org/jira/browse/JBESB-2335 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.5 -- 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

17 years, 2 months

2
11
0 / 0

[JBoss JIRA] Created: (JBESB-2316) Support querying of process instance variables

by Kevin Conner (JIRA)

Support querying of process instance variables ---------------------------------------------- Key: JBESB-2316 URL: https://jira.jboss.org/jira/browse/JBESB-2316 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 Add support for querying process instance variables (i.e. those of the root token). -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2331) JBrules deployment error when deploying to JBossAS

by Daniel Bevenius (JIRA)

JBrules deployment error when deploying to JBossAS -------------------------------------------------- Key: JBESB-2331 URL: https://jira.jboss.org/jira/browse/JBESB-2331 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.5 TomF reported this error upon deploying to JBossAS: 08:36:18,799 INFO [JmxKernelAbstraction] installing MBean: persistence.units:unitName=org.drools.persistence.jpa with dependencies: 08:36:18,801 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:unitName=org.drools.persistence.jpa 08:36:18,813 WARN [ServiceController] Problem starting service persistence.units:unitName=org.drools.persistence.jpa java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: org.drools.persistence.jpa at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:220) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) ... 08:36:18,930 INFO [EJB3Deployer] Deployed: file:/opt/jboss/as/4.2.3/jboss-4.2.3.GA/server/default/deploy/jbrules.esb/drools-process-enterprise-5.0.0.M4.jar 08:36:18,936 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment 08:36:18,937 INFO [JmxKernelAbstraction] installing MBean: persistence.units:unitName=org.drools.task with dependencies: 08:36:18,938 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:unitName=org.drools.task 08:36:18,944 WARN [ServiceController] Problem starting service persistence.units:unitName=org.drools.task java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: org.drools.task at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:220) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) I'm also seeing this upon startup but it's not related to drools: 08:35:12,111 INFO [InventoryManager] Detected new Server [Resource[id=-4, type=Embedded Tomcat Server, key=jboss-web.deployer, name=danbev-laptop Embedded JBossWeb Server 2.0.1.GA (127.0.0.1), version=2.0.1.GA]] - adding to local inventory... 08:35:12,258 WARN [RuntimeDiscoveryExecutor] Failed to execute runtime discovery for Resources of type ResourceType[id=0, category=Service, name=JBossMQ, plugin=JBossAS] java.lang.ClassCastException: org.jboss.mq.server.JMSDestinationManager at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.getVersionFromSource(AbstractMessagingDiscoveryComponent.java:107) at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.discoverResources(AbstractMessagingDiscoveryComponent.java:72) at org.rhq.plugins.jbossas.JBossMQDiscoveryComponent.discoverResources(JBossMQDiscoveryComponent.java:44) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.executeComponentDiscovery(RuntimeDiscoveryExecutor.java:246) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:218) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:136) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:97) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:54) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168) 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

17 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2333) EBWS test failure under jdk1.6

by Kevin Conner (JIRA)

EBWS test failure under jdk1.6 ------------------------------ Key: JBESB-2333 URL: https://jira.jboss.org/jira/browse/JBESB-2333 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP2 The EBWS unit test is failing under jdk 1.6 because of the following server side exception 2008-10-22 10:38:11,258 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:67) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:207) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:185) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:389) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) -- 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

17 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2332) business_ruleservice_ruleAgent quickstart error

by Daniel Bevenius (JIRA)

business_ruleservice_ruleAgent quickstart error ----------------------------------------------- Key: JBESB-2332 URL: https://jira.jboss.org/jira/browse/JBESB-2332 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Fix For: 4.5 The following error will be generated when running the quickstart: 14:06:50,181 INFO [STDOUT] Message before transformation: 14:06:50,181 INFO [STDOUT] [<Policy type="COMPREHENSIVE" > <Driver name="Bill Smith" age="30" priorClaims="0" locationRiskProfile="LOW" /> </Policy> ]. 14:06:50,660 INFO [SetupMessage] Moved the transformed driver and policy 14:06:50,723 ERROR [STDERR] RuleAgent(insuranceconfig) INFO (Tue Feb 03 14:06:50 CET 2009): Configuring with newInstance=true, secondsToRefresh=30 14:06:50,724 ERROR [STDERR] RuleAgent(insuranceconfig) INFO (Tue Feb 03 14:06:50 CET 2009): Configuring package provider : FileScanner scanning: /opt/jboss/esb/trunk/product/samples/quickstarts/business_ruleservice_ruleAgent/ruleAgent/package/org.jboss.soa.esb.services.rules.pkg 14:06:50,864 ERROR [STDERR] RuleAgent(insuranceconfig) EXCEPTION (Tue Feb 03 14:06:50 CET 2009): No ClassLoaders found for: org.drools.rule.PackageCompilationData. Stack trace should follow. 14:06:50,864 ERROR [STDERR] java.lang.ClassNotFoundException: No ClassLoaders found for: org.drools.rule.PackageCompilationData 14:06:50,864 ERROR [STDERR] at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306) 14:06:50,864 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521) 14:06:50,864 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415) 14:06:50,864 ERROR [STDERR] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) 14:06:50,864 ERROR [STDERR] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) 14:06:50,864 ERROR [STDERR] at java.lang.Class.forName0(Native Method) 14:06:50,864 ERROR [STDERR] at java.lang.Class.forName(Class.java:242) 14:06:50,864 ERROR [STDERR] at org.drools.common.DroolsObjectInputStream.resolveClass(DroolsObjectInputStream.java:72) 14:06:50,864 ERROR [STDERR] at org.drools.common.DroolsObjectInputStream.resolveClass(DroolsObjectInputStream.java:84) 14:06:50,864 ERROR [STDERR] at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544) 14:06:50,864 ERROR [STDERR] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) 14:06:50,864 ERROR [STDERR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) 14:06:50,865 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) 14:06:50,865 ERROR [STDERR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) 14:06:50,865 ERROR [STDERR] at org.drools.rule.Package.readExternal(Package.java:197) 14:06:50,865 ERROR [STDERR] at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755) 14:06:50,865 ERROR [STDERR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717) 14:06:50,865 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) 14:06:50,865 ERROR [STDERR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) 14:06:50,865 ERROR [STDERR] at org.drools.util.DroolsStreamUtils.streamIn(DroolsStreamUtils.java:189) 14:06:50,865 ERROR [STDERR] at org.drools.util.DroolsStreamUtils.streamIn(DroolsStreamUtils.java:158) 14:06:50,865 ERROR [STDERR] at org.drools.agent.FileScanner.readPackage(FileScanner.java:136) 14:06:50,865 ERROR [STDERR] at org.drools.agent.FileScanner.getChangeSet(FileScanner.java:82) 14:06:50,865 ERROR [STDERR] at org.drools.agent.FileScanner.loadPackageChanges(FileScanner.java:56) 14:06:50,865 ERROR [STDERR] at org.drools.agent.RuleAgent.checkForChanges(RuleAgent.java:401) 14:06:50,865 ERROR [STDERR] at org.drools.agent.RuleAgent.refreshRuleBase(RuleAgent.java:353) 14:06:50,865 ERROR [STDERR] at org.drools.agent.RuleAgent.configure(RuleAgent.java:338) 14:06:50,865 ERROR [STDERR] at org.drools.agent.RuleAgent.init(RuleAgent.java:247) 14:06:50,865 ERROR [STDERR] at org.drools.agent.RuleAgent.newRuleAgent(RuleAgent.java:187) 14:06:50,865 ERROR [STDERR] at org.drools.agent.RuleAgent.newRuleAgent(RuleAgent.java:147) 14:06:50,865 ERROR [STDERR] at org.drools.agent.RuleAgent.newRuleAgent(RuleAgent.java:256) 14:06:50,865 ERROR [STDERR] at org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseHelper.createRuleAgent(DroolsRuleBaseHelper.java:226) 14:06:50,865 ERROR [STDERR] at org.jboss.internal.soa.esb.services.rules.DroolsRuleService.getRuleBaseForRuleAgent(DroolsRuleService.java:613) 14:06:50,865 ERROR [STDERR] at org.jboss.internal.soa.esb.services.rules.DroolsRuleService.executeStatelessRulesFromRuleAgent(DroolsRuleService.java:175) 14:06:50,865 ERROR [STDERR] at org.jboss.internal.soa.esb.services.rules.RuleServiceCallHelper.executeRulesService(RuleServiceCallHelper.java:141) 14:06:50,865 ERROR [STDERR] at org.jboss.soa.esb.actions.BusinessRulesProcessor.executeRulesService(BusinessRulesProcessor.java:121) 14:06:50,907 ERROR [STDERR] at org.jboss.soa.esb.actions.BusinessRulesProcessor.process(BusinessRulesProcessor.java:97) 14:06:50,907 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:615) 14:06:50,907 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:574) 14:06:50,907 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:408) 14:06:50,907 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:548) 14:06:50,907 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) 14:06:50,907 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) 14:06:50,907 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) 14:06:50,907 ERROR [STDERR] RuleAgent(insuranceconfig) WARNING (Tue Feb 03 14:06:50 CET 2009): Was unable to load a class when loading a package. Perhaps it is missing from this application. 14:06:51,085 INFO [STDOUT] { ================ Sent notification: 14:06:51,085 INFO [STDOUT] Name: Bill Smith 14:06:51,085 INFO [STDOUT] Policy Price: 0 14:06:51,085 INFO [STDOUT] } ================ Sent notification: -- 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

17 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1984) XSD validation in AbstractProcessingPipeline can fail in legacy environments

by Jiri Pechanec (JIRA)

XSD validation in AbstractProcessingPipeline can fail in legacy environments ---------------------------------------------------------------------------- Key: JBESB-1984 URL: https://jira.jboss.org/jira/browse/JBESB-1984 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Jiri Pechanec Priority: Critical In AbstractProcessingPipeline the message payload is accessed by direct call of message.get() for purpose of XSD validations. I thing the access should be via MessagePayloadProxy class as in other parts of the codebase to work correctly in legacy environment. -- 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

17 years, 2 months

2
11
0 / 0

[JBoss JIRA] Created: (JBESB-2233) Identify 4.4CP2 issues that need merging to trunk

by Kevin Conner (JIRA)

Identify 4.4CP2 issues that need merging to trunk ------------------------------------------------- Key: JBESB-2233 URL: https://jira.jboss.org/jira/browse/JBESB-2233 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 A number of issues have already been fixed for 4.4CP2, most of which are still applicable to trunk. Go through the issues, applying them individually to trunk. -- 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

17 years, 2 months

1
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2009