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

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Reimplementing ClassPools for AS

by adrian＠jboss.org

"alesj" wrote : | I guess it doesn't do any harm ... Yes it does potential harm because you can get access to classes and resources from other classes that you shouldn't be allowed to. e.g. in your example you can load unexported classes from fcl which you can't do from cl That's why you need the RuntimePermission("getClassLoader") like you do for class.getClassLoader(). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201417#4201417 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201417

17 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Reimplementing ClassPools for AS

by alesj

"adrian(a)jboss.org" wrote : | See BaseClassLoader.getClassLoaderForClass() for how it works | without exposing nasty things. ;-) | You can do this | public ClassLoader foo(ClassLoader cl) throws Exception | { | ClassLoader fcl = null; | if (cl instanceof BaseClassLoader) | { | BaseClassLoader bcl = (BaseClassLoader)cl; | fcl = bcl.findClassLoader("com.acme.FooBar"); | } | return fcl; | } | Intentional? I guess it doesn't do any harm ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201412#4201412 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201412

17 years, 2 months

1
0
0 / 0

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

by alex.loubyansky＠jboss.com

Yes, if you apply @JBossXmlNsPrefix to sipServlets then servlet element will be in the javaee namespace, so in xml you'll have 'javaee:servlet'. If you can't get it to work please create a testcase somewhere (metadata preferable but you might not have commit rights) or send it to me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201411#4201411 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201411

17 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Reimplementing ClassPools for AS

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : I've uploaded a 2.0.2-SNAPSHOT of jboss-cl for you to try. | | This has a Module.getModuleForClass() which at least for our classloader implementation | doesn't load the class. | If somebody wants to integrate their classloader implementation (there are no others at the moment since we decied to drop the old UnifiedClassLoader :-) properly with AOP then they'll have to override this method to give the correct semantics. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201410#4201410 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201410

17 years, 2 months

1
0
0 / 0

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

by deruelle_jean

I copied paste the wrong exception sorry (this is because I tried it on listener as well) so I have to duplicate the existing classes in metadata that are used by the sipapp xsd such as servletType(ServletsMetaData and ServletMetatData) or listenerType(ListenerMetaData) or another way would be to add those JBossXmlNs to the classes in the metadata project maybe : org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/deruelle/servers/jboss-5.0.0.GA/server/default/deploy/call-blocking-1.2-SNAPSHOT.war at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: {http://www.jcp.org/xml/ns/sipservlet}servlet not found as a child of {http://www.jcp.org/xml/ns/sipservlet}sip-app 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: {http://www.jcp.org/xml/ns/sipservlet}servlet not found as a child of {http://www.jcp.org/xml/ns/sipservlet}sip-app at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:400) 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.impl.xs.XMLSchemaValidator.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) ... 30 more View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201408#4201408 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201408

17 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Reimplementing ClassPools for AS

by adrian＠jboss.org

I've uploaded a 2.0.2-SNAPSHOT of jboss-cl for you to try. This has a Module.getModuleForClass() which at least for our classloader implementation doesn't load the class. See BaseClassLoader.findClassLoaderForClass() for how it works without exposing nasty things. ;-) You'll need to put its use in a privileged block since I require the new RuntimePermission("getClassLoader") with a security manager installed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201405#4201405 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201405

17 years, 2 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - JBoss 4.2 and JEE 5 - components out of compliance

by doug.lundin＠gmail.com

All, Trying to answer this question, "If we build out against JBoss 4.2, what capabilities will be unavailable to clients developed in JEE 5" Understand this is a multi-level question but am hoping to get answers such as "well, EJB3 is JEE 5 but wouldn't be supported by JBoss 4.2" Suspecting this is a TCK-related question so this is the appropriate forum - please let me know if that is not the case. Cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201403#4201403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201403

17 years, 2 months

1
0
0 / 0

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

by alex.loubyansky＠jboss.com

There is nothing about the servlet element in the error. You have to annotate listener with JBossXmlNsPrefix as well. I don't see why you have to duplicate anything so far. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201402#4201402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201402

17 years, 2 months

1
0
0 / 0

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

by deruelle_jean

It works if I duplicate the original ServletsMetaData and ServletMetaData classes and put the new annotation @JBossXmlNsPrefix(prefix="javaee", schemaTargetIfNotMapped=true) Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201401#4201401 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201401

17 years, 2 months

1
0
0 / 0

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

by deruelle_jean

it doesn't work for my usecase but after some thoughts maybe it's normal see my comments below the stacktrace org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/deruelle/servers/jboss-5.0.0.GA/server/default/deploy/call-blocking-1.2-SNAPSHOT.war at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: {http://www.jcp.org/xml/ns/sipservlet}listener not found as a child of {http://www.jcp.org/xml/ns/sipservlet}sip-app 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: {http://www.jcp.org/xml/ns/sipservlet}listener not found as a child of {http://www.jcp.org/xml/ns/sipservlet}sip-app at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:400) 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.impl.xs.XMLSchemaValidator.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) ... 30 more I think this is because servlet element is still in the sipservlet namespace only the childs of servlet element are in the javaee namespace (because the servlet element which is present in the sipapp xsd uses the servletType of the javaee schema). So I wonder if I have any other choice than duplicating those classes... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201396#4201396 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201396

17 years, 2 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 January 2009