April 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by deruelle_jean

"alex.loubyansky(a)jboss.com" wrote : If that's a choice binding based on a super class then you could try: | ] Not it is not. it is a substitution group. I tried anyway but I got Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Requested element and is not allowed in this position in the sequence. The next element should be condition | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) | at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199) | at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170) | at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) | at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:323) | ... 22 more | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Requested element and is not allowed in this position in the sequence. The next element should be condition | at org.jboss.xb.binding.sunday.unmarshalling.SequenceBinding$1.startElement(SequenceBinding.java:226) | at org.jboss.xb.binding.sunday.unmarshalling.ModelGroupBinding$Cursor.startElement(ModelGroupBinding.java:185) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:397) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) | at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) | at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) | at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) I committed everything to SVN in case you want take a look at it. But I think I find some tips after some time googling around : http://java.sun.com/javaee/5/docs/api/javax/xml/bind/annotation/XmlElemen... Example 2 and http://fusesource.com/docs/framework/2.1/jaxws/JAXWSElementSubstitutionJa... I hope this will help. If you have any similarity in JBoss metadata somewhere that would be helpful Thanks in advance Best regards Jean View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227857#4227857 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227857

15 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - EJB3 Plugin now targets JBoss AS 5.1.0 CR1

by jaikiran

Now that the 5.1.0 CR1 AS has been released http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154602, the plugin will now target this new version. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227852#4227852 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227852

15 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: javax.ejb.EJB Annotations Outside EJB3 Components

by jaikiran

anonymous wrote : Above usecase doesn't work because I don't know how to construct/obtain injected EJB3 JNDI name. We have a EJBReferenceResolver http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/common/src/mai... which, given a deployment unit and an EJBReference http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/common/src/mai... resolves the JNDI name. Ex: http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/common/src/mai... The only thing i am not sure is whether non-EJB3 components (like JBossWS) can use this (i.e. add a dependency on this). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227843#4227843 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227843

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Boolean properties in RA not following standard conventi

by clebert.suconic＠jboss.com

I was going to bring this up on forums when I did I mean.. when I was working on the JCA adapter. I had issues with some of the properties not being picked up by introspection. but I' m not the one who originally made everything set/get. ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227830#4227830 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227830

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Boolean properties in RA not following standard conventi

by clebert.suconic＠jboss.com

I was going to bring this up on forums when I did.. but for some reason I forgot. JMX uses instrospection to access those properties. And those properties are the type class Boolean. (not native boolean). for boolean, java Beans introspection will define those as isProp and setProp For Boolean, java Beans introspection will define those as setProp and getProp. We need to decide which one we are going to use. As right now those get are not being introspected. It' s like those properties are write only. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227829#4227829 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227829

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Boolean properties in RA not following standard conventi

by ataylor

I guess probably because it wasn't originally written by one of our team. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227817#4227817 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227817

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Boolean properties in RA not following standard conventions

by timfox

Why are boolean resource adapters not following the standard isXXX()/setXXX() convention, and instead use getXXX()/setXXX() ?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227793#4227793 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227793

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Potential Netty problem with synchronously closing conne

by timfox

As a note if I add a small sleep (100 ms) between each connection creation and close, then the test will run ad-infinitum with no problems. The test is org.jboss.test.messaging.jms.ConnectionTest::testConnectionListenerBug View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227772#4227772 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227772

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Potential Netty problem with synchronously closing connectio

by timfox

We have a JBM test which quickly creates and closes connections in a loop which eventually fails with: | New I/O server boss #1 (channelId: 28338721, /127.0.0.1:5445) 11:41:29,851 WARN [NioServerSocketPipelineSink] Failed to accept a connection. | java.io.IOException: Too many open files | at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) | at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:145) | at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.run(NioServerSocketPipelineSink.java:205) | 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) | Creating a JBM JMS and closing it involves creating a Netty bootstrap, creating a channel, closing the channel and closing the bootstrap. This is done in quick succession. Debugging this a bit, it seems that the netty channel disconnected event can arrive at the server significantly later than when the channel is closed from the client side. So.. over time we end up with the rate of creating channels exceeds the rate that channel disconnected arrives at the server and the server soon runs out of file handles. I would have thought disconnection would be synchronous, otherwise a client could easily create a DoS attack. Any ideas? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227770#4227770 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227770

15 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: javax.ejb.EJB Annotations Outside EJB3 Components

by jaikiran

"richard.opalka(a)jboss.com" wrote : | Also javax.ejb.EJB annotation is really confusing me. What's the difference between name and mappedName? | The "name" attribute is jndiname within the java:comp/env namespace of the component into which the bean is being injected. So if you have: | @Stateless | public AnotherBean... | { | | @EJB(name="someName") | private BeanOne bean; | .. | } This means that the BeanOne is available at java:comp/env/someName jndiname of the AnotherBean's java:comp/env namespace. The mappedName is actually the global jndiname (not the java:comp/env namespace) of the bean. The mappedName is actually not portable. Each vendor (application server) can implement this the way they want and are even allowed to ignore it. anonymous wrote : Where in the EJB spec I can find exhausting description of this annotation? I found this useful http://java.sun.com/products/ejb/javadoc-3_0-fr/javax/ejb/EJB.html View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227767#4227767 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227767

15 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2009