October 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBossXB] - Re: @XmlElementWrapper/@XmlElements

by alex.loubyansky＠jboss.com

I am looking into this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094060#4094060 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094060

18 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Failed to create a new SAX parser

by thomas.diesler＠jboss.com

Folks, have you seen this? | org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser | at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100) | at org.jboss.ws.metadata.config.JBossWSConfigFactory.parse(JBossWSConfigFactory.java:76) | at org.jboss.ws.metadata.config.JBossWSConfigFactory.getConfig(JBossWSConfigFactory.java:134) | at org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfig(EndpointMetaData.java:705) | at org.jboss.ws.metadata.umdm.EndpointMetaData.setConfigNameInternal(EndpointMetaData.java:696) | at org.jboss.ws.metadata.umdm.EndpointMetaData.setConfigName(EndpointMetaData.java:680) | at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.processEndpointConfig(JAXWSServerMetaDataBuilder.java:76) | at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:137) | at org.jboss.ws.tools.jaxws.impl.JBossWSProviderImpl.provide(JBossWSProviderImpl.java:107) | at org.jboss.ws.tools.jaxws.impl.JBossWSProviderImpl.provide(JBossWSProviderImpl.java:123) | at org.jboss.wsf.spi.tools.ant.WSProvideTask.executeNonForked(WSProvideTask.java:221) | at org.jboss.wsf.spi.tools.ant.WSProvideTask.execute(WSProvideTask.java:237) | at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) | at org.apache.tools.ant.Task.perform(Task.java:364) | at org.apache.tools.ant.Target.execute(Target.java:341) | at org.apache.tools.ant.Target.performTasks(Target.java:369) | at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) | at org.apache.tools.ant.Project.executeTarget(Project.java:1185) | at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) | at org.apache.tools.ant.Project.executeTargets(Project.java:1068) | at org.apache.tools.ant.Main.runBuild(Main.java:668) | at org.apache.tools.ant.Main.startAnt(Main.java:187) | at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) | at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) | Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.<init>(SaxJBossXBParser.java:101) | at org.jboss.xb.binding.UnmarshallerImpl.<init>(UnmarshallerImpl.java:55) | at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:96) | ... 23 more | Caused by: java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null" | at javax.xml.parsers.SAXParser.isXIncludeAware(SAXParser.java:511) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.<init>(SaxJBossXBParser.java:93) | ... 25 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094059#4094059 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094059

18 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - MessageDriven tests in jboss-head

by adrian＠jboss.org

WRT: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120986 I fixed up these tests so they are at least running. Like I said originally, these tests should have been changed to use a pluggable JMSAdmin class rather the hacks that are currently present. :-( The test for restarting the JMS needs implementing, it is not an irrelevant test like the comment in code stated. Similary the problems with rebooting JBossMessaging I mentioned in different thread a few months ago are still not fixed. The topic tests for "deliveryActive" are currently failing. I think this is probably a race condition (i.e. the subscription is not yet created when the message is sent?) in the test but it needs confirming. Finally, when I copy the test-destinations-full-service.xml to the deploy directory and boot the server, I'm seeing "random" NPEs from the PostOffice "getInstance" operation (it's not easy to reproduce - sorry no stacktrace). Again, this looks like a race since if I touch the file after the server is fully booted, it fixes itself (at least I've never seen the NPE with a fully booted server). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094050#4094050 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094050

18 years, 6 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-4517 -

by adrian＠jboss.org

Also while I was doing this, I made some improvements to the synchronization of the MessageEndpointInterceptor and JmsActivation to make it more thread safe. This is probably not a real issue, but these could do with backporting to JBoss-4.2 as well in the next stable release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094043#4094043 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094043

18 years, 6 months

1
0
0 / 0

[Design of JCA on JBoss] - JBAS-4517 - "Removal" of JMSContainerInvoker in head

by adrian＠jboss.org

I've converted the old JMSContainerInvoker in jboss-head to use the JCA 1.5 inbound resource adapter. This involved: * Changing the JMSContainerInvoker class to just be a hardwired version of an inflow mdb deployment. i.e. it now extends the JBossJMSMessageEndpointFactory * Added support for start/stopDelivery() to the JBossMessageEndpointFactory * Added the old JMSContainerInvoker JMX notifications to the JmsActivation * Completing the mapping of the old DLQ config in the JBossJMSMessageEndpointFactory * While I was there, I did some work on making the MessageEndpointInterceptor and the JmsActivation a bit more thread safe Comments 1) I haven't written the tests for the start/stopDelivery() of the normal inflow container. We also need a "deliveryActive" configuration for the inflow invoker-proxy-binding config so you can deploy an inflow MDB in the inactive state. 2) The start/stopDelivery() tests of the JMSContainerInvoker are failing for topics. I think this relates to the startDelivery() being asynch so the initialization of topic subscription is racing with the send()? But need to verify this. 3) The JmsActivationSpec has no support for DLQ "time-to-live" this needs adding the jms inbound resource adapter for backwards compatibility 4) There are some methods in the JMSContainerInvoker JMX interface that are not implemented. Not sure if we want to support these since the the profile service is probably a better way to do what this doing? 5) There is no longer any support for createJBossMQDestination(). If we really want to support this (I don't :-) then it should be some kind of a plugin to the jms resource adapter (maybe a factory class passed into the activation spec?) 6) The restartJMS() test is not implemented for JBoss Messaging, something I'll take up in the jms forum. All these tests were very broken in jboss-head anyway! :-( 7) I kept the old JMSContainerInvoker notifications names for backwards compatibility, e.g. org.jboss.ejb.plugins.jms.CONNECTING, rather than org.jboss.resource.adapter.jms.inflow.CONNECTING 8) The support for the old JMSContainerInvoker notifications is a hack. It's based on the JBossMessageEndpointFactory implementing JBossNotificationBroadcasterSupport (something the EJB3 container doesn't do!). This needs doing in a better way. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094040#4094040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094040

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Getting runtime component name from attachment

by alesj

OK, just saw that my initial impl was a total crap. But I also saw that we already have an attachment aware interface - InstanceClassFactory. I can just add a getComponentName method there. And I'll still leave the @ManagedRuntimeRef if a mbean/service explicitly marks some property as component name provider. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094037#4094037 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094037

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Schema validation for ejb-jar.xml

by adrian＠jboss.org

I've turned off schema validation for ejb-jar.xml (for backwards compatibility) otherwise some of the tests don't pass that do system property replacement or xml enums, e.g. the message driven tests where transaction-type should be "container" or "bean" according the schema | <message-driven> | <ejb-name>TestMDB</ejb-name> | <ejb-class>org.jboss.test.messagedriven.beans.TestMessageDriven</ejb-class> | <messaging-type>javax.jms.MessageListener</messaging-type> | <transaction-type>${test.messagedriven.transactionType}</transaction-type> | We probably want to revisit this test so we can enable schema validation by default? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094030#4094030 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094030

18 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Problem facing while implementing example helloworld_ftp

by Kevin.Conner＠jboss.com

This is not the correct forum, moving this to the user forum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093996#4093996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093996

18 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Problem facing while implementing example helloworld_ftp_act

by sagar_atikam

Hi, While implementing example jbossesb-4.2MR3\samples\quickstarts\helloworld_ftp_action I am a facing problem. I had configured a connection to local FTP server from JBoss ESB to read message from FTP server location, but ended up with following exception: [java] Reading config from E:\jbossesb-4.2MR3\samples\quickstarts\helloworld_ftp_action\jboss-esb.xml [java] 16:19:41,824 ERROR [Thread-2][EdtFtpImpl] Caught FTPException. [java] com.enterprisedt.net.ftp.FTPException: File renamed [java] at com.enterprisedt.net.ftp.FTPControlSocket.validateReply(FTPControlSocket.java:923) [java] at com.enterprisedt.net.ftp.FTPClient.rename(FTPClient.java:2494) [java] at org.jboss.internal.soa.esb.util.EdtFtpImpl.remoteRename(EdtFtpImpl.java:489) [java] at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.renameFile(RemoteGatewayListener.java:208) [java] at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.doRun(AbstractFileGateway.java:141) [java] at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) [java] at java.lang.Thread.run(Thread.java:595) [java] 16:19:41,887 ERROR [Thread-2][AbstractFileGateway] Problems renaming file HWFtp-11-Oct-07-15-41-00.dat to HWFtp-11-Oct-07-15-41-00.dat.esbInProcess In readme.txt file, it is specified that ?this problem will come when we don?t have write permission on remote FTP server location?. But I had given full permissions on remote FTP server location. Did I missed any other configuration settings? I am using FTP server: Xlight FTP server JBoss ESB: jbossesb-4.2MR3 JBoss AS: jboss-4.0.5.GA Please pour some inputs. Thanks, -Vidya View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093987#4093987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093987

18 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: [sim] language features

by camunda

Hi Ronald, for the moment I would pospone that proposal, because I think it is not really the intension of a business process simulation (BPS) tool. I see two possible situations: - actions/scripts doe something sychronous: This only needs computing time, which is irrelevant for simulation. If the computing needs some special resource to be evailable, it shouldn't be synchronous, because what to do if the resource is not available? - actions/scripts doe something asychronous. Normaly this happens at the node-enter of some state. The state then waits for the results. This can already be realized by the current features set with a time-distribution for states. Or do you have something in mind which doesn't fit here? But I also want to agree on this sentence, so we may just wait: anonymous wrote : | For the rest, I'd say lets just see where this takes us... anonymous wrote : Besides that, would be nice to display the result of a sim from the database in something like www.pentaho.org Agreed. But reports & result visualization is out of scope for the moment... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093983#4093983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093983

18 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2007