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

[Design of JBossXB] - Re: XsdBinder status

by alex.loubyansky＠jboss.com

It is still used in WS for example. But I don't understand the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095367#4095367 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095367

18 years, 5 months

1
0
0 / 0

[Design of JBossXB] - XsdBinder status

by scott.stark＠jboss.org

I ran into an error in the jboss-metadata project where a ejb-jar.xml that was parsed in one test failed to parse in another. It turned out the schema resolver has not been configured correctly in the latter case, and the XsdBinder was being used to build the schema from the xsd rather than the xsd location being mapped to the EjbJar21MetaData jaxb annotated class in the passing test. We do use the XsdBinder for a number of schemas. I guess it cannot handle the ejb-jar_2_1.xsd though. I expect we are moving toward the jaxb/jbossxb annotations and deprecating XsdBinder? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095362#4095362 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095362

18 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: So what does unification mean for the ejb containers

by scott.stark＠jboss.org

The schemas/dtds need to be in the jar for classpath resource resolution. They were previously in the jboss.jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095344#4095344 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095344

18 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Integration on JBoss5: NullPointerException deploying jm

by scott.stark＠jboss.org

Yes, see the metadata discussion. The trunk as been switched to use the jboss-metadata project, which uses jaxb style processing. This means unspecified elements will be null rather than empty was was the case before. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095343#4095343 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095343

18 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Integration on JBoss5: NullPointerException deploying jmsra.

by clebert.suconic＠jboss.com

Something was changed on the Application Server. When I execute the org.jboss.test.jbossmessaging.ra.RaJMSSessionUnitTestCase I'm getting a NPE, because of the deployment of /extra/clebert/workspaces/svn-trunk-jboss/trunk/testsuite/output/lib/jmsra.jar 12:03:59,760 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/extra/clebert/workspaces/svn-trunk-jboss/trunk/testsuite/output/lib/jmsra.jar state=Not Installed mode=Manual requiredState=Parse | org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/extra/clebert/workspaces/svn-trunk-jboss/trunk/testsuite/output/lib/jmsra.jar | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:232) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:199) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:812) | 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | 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.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:270) | 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) | at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) | 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:815) | at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:416) | 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) | at sun.rmi.transport.Transport$1.run(Transport.java:153) | at java.security.AccessController.doPrivileged(Native Method) | at sun.rmi.transport.Transport.serviceCall(Transport.java:149) | at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) | at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) | at java.lang.Thread.run(Thread.java:595) | Caused by: java.lang.NullPointerException | at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60) | at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57) | at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104) | at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223) | ... 65 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095335#4095335 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095335

18 years, 5 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Customized LoginModule

by anil.saldhana＠jboss.com

In 2 days, I am moving this thread to the security user forum. This is for design of JBoss security. Not user questions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095328#4095328 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095328

18 years, 5 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Customized LoginModule

by sguilhen＠redhat.com

If I understood your problem correctly, you want to collect some client data and pass this data to the container for authentication, but you need customized login modules to handle the ip address. Section 8.4 of the following documentation may be of some help, as it describes how to customize the login modules: http://docs.jboss.org/jbossas/jboss4guide/r5/html/ch8.chapter.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095327#4095327 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095327

18 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: So what does unification mean for the ejb containers

by anil.saldhana＠jboss.com

carlo, not sure if this is relevant. I saw that u added the schema to src/resources in the metadata project. Just remember that maven will add the schema to the metadata jars. If that is not intended and the xsd is just for the tests, then it needs to go to test/resources or such. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095325#4095325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095325

18 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: So what does unification mean for the ejb containers

by wolfc

In the original xsd we also have ejb-name defined, so I'm now using that one. I've also updated JBossXBTestDelegate to make schema validation an option. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095322#4095322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095322

18 years, 5 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ClassLoading Module usage

by scott.stark＠jboss.org

Then we need an in memory vfs uri handler that can load the generated classes from a uri like vfsmemory:/aop-domain/classes. I thought Bill had done some work along the lines of an in memory vfs handler, but I don't see a url handler for it. There are org.jboss.virtual.plugins.context.vfs.AssembledDirectory/AssembledFile that allow for virtual aggregating directories/files on top of other vfs urls, but not an in memory type. Its easy enough to add such a handler. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095296#4095296 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095296

18 years, 5 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