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

[Design of JBoss ESB] - Re: Big changes in deployment, distribution, and testing

by poyge394

Nice, is this changes coming in next release ? and witch date is the next release coming ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029239#4029239 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029239

19 years

1
0
0 / 0

[Other JBoss Development Design] - connecconnect Microsoft IIS to JBoss App Server

by akanshakumarbe

I have an IIS server installed. I have developed my J@EE application with JBoss IDE.now i want to connect this to the IIS server. Is this possible... If yes please give me some details/pointers . Thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029218#4029218 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029218

19 years

1
0
0 / 0

[Design of POJO Server] - Re: AOP testsuite failures in AS trunk

by scott.stark＠jboss.org

The SecurityDeployer is only creating the mbean for the top level deployment. For the deployment in question, there are no nested deployments. There is a problem with the way the mc is handling deployments with multiple component types. Maybe before the check for whether the deployment was top-level was an issue, but with that in place, its not creating duplicate deployment content. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029199#4029199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029199

19 years

1
0
0 / 0

[Design of JBoss Build System] - Mavenizing docbook project

by anil.saldhana＠jboss.com

The Doc Book project uses ant for building. Are there any plans with migrating this to a maven setup? There is a maven docbook plugin available. I went through the JIRA issues for JBBUILD and I did not see one for docbook. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029198#4029198 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029198

19 years

1
0
0 / 0

[Design of POJO Server] - Re: AOP testsuite failures in AS trunk

by anil.saldhana＠jboss.com

The SecurityDeployer AFAIR JaccPolicy beans for nested deployments only if there are JACC capable deployments underneath (wars, ejb jars). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029197#4029197 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029197

19 years

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by scott.stark＠jboss.org

That looks like a problem with the org.jboss.aop.ClassContainer not using the correct class loader. Create a jira issue describing the deployer descriptor in use and ask Kabir to look at it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029187#4029187 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029187

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Embedded FTP Server and FTP Clients

by kukeltje

The jBPM dev forum would be a great place. I know Tom has some ideas in this area (I just know some basics ;-) ) but he's not quite sure how to implement it (afaik, but that could have changed). And yes, you are right about needing a controler, and right again about it being used atm, but afaik in fairly controled environments, not in 'just any webservice based service between random organisations' View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029185#4029185 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029185

19 years

1
0
0 / 0

[Design of POJO Server] - Re: AOP testsuite failures in AS trunk

by scott.stark＠jboss.org

Its a bug in the processing of a deployment with multiple component types ( http://jira.jboss.com/jira/browse/JBMICROCONT-159). Its not really a SecurityDeployer problem, although it should be creating a ServiceDeployment that contains the ServiceMetaData for the JaccPolicy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029184#4029184 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029184

19 years

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by weston.price＠jboss.com

I am running into a problem using the JAXB deployer from the MC (2.0.0Beta3). For some reason, the deployer can't be initialized: | | 21:38:50,428 ERROR [AbstractKernelController] Error installing to Described: name=ManagedConnectionFactoryParserDeployer state=PreInstall | java.lang.NoClassDefFoundError: Ljavax/xml/bind/JAXBContext; | at java.lang.Class.getDeclaredFields0(Native Method) | at java.lang.Class.privateGetDeclaredFields(Class.java:2232) | at java.lang.Class.getDeclaredFields(Class.java:1715) | at org.jboss.aop.ClassContainer$1.run(ClassContainer.java:93) | at java.security.AccessController.doPrivileged(Native Method) | at org.jboss.aop.ClassContainer.populateFieldTable(ClassContainer.java:89) | at org.jboss.aop.ClassContainer.populateFieldTable(ClassContainer.java:84) | at org.jboss.aop.ClassContainer.createFieldTable(ClassContainer.java:114) | at org.jboss.aop.ClassContainer.initializeMetadata(ClassContainer.java:72) | at org.jboss.aop.ClassContainer.initializeClassContainer(ClassContainer.java:59) | at org.jboss.aop.proxy.container.ClassProxyContainer.initialise(ClassProxyContainer.java:174) | at org.jboss.aop.proxy.container.ContainerCache.createContainer(ContainerCache.java:183) | at org.jboss.aop.proxy.container.ContainerCache.createAndCacheContainer(ContainerCache.java:171) | at org.jboss.aop.proxy.container.ContainerCache.initClassContainer(ContainerCache.java:159) | at org.jboss.aop.proxy.container.ContainerCache.initialise(ContainerCache.java:92) | at org.jboss.aop.proxy.container.ContainerCache.initialise(ContainerCache.java:72) | at org.jboss.aop.microcontainer.integration.AOPDependencyBuilder.getDependencies(AOPDependencyBuilder.java:91) | at org.jboss.classadapter.plugins.BasicClassAdapter.getDependencies(BasicClassAdapter.java:79) | at org.jboss.beans.info.plugins.AbstractBeanInfo.getDependencies(AbstractBeanInfo.java:210) | at org.jboss.kernel.plugins.dependency.DescribeAction.installActionInternal(DescribeAction.java:54) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:67) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:42) | at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:56) | at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) | at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:592) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:603) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:476) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:406) | 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.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:121) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:110) | at org.jboss.profileservice.aop.MainDeployerAspect.process(MainDeployerAspect.java:53) | at org.jboss.aop.advice.org.jboss.profileservice.aop.MainDeployerAspect_z_process_10062600.invoke(MainDeployerAspect_z_process_10062600.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at AOPContainerProxy$0.process(AOPContainerProxy$0.java) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:364) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:247) | at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) | at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403) | at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342) | at org.jboss.Main.boot(Main.java:210) | at org.jboss.Main$1.run(Main.java:522) | at java.lang.Thread.run(Thread.java:613) | | I had initially thought that it was the version of JAXB I had compiled against, but this does not appear to be the case as I have tried multiple versions to no avail. I then thought it might be simply that the classes cannot be found but I tried putting them in the usual places (ie server/lib etc) also to no avail. Also, currently the JAXB deployer only allows for a single type in the instantiation of the JAXBContext | | if (properties != null) | context = JAXBContext.newInstance(new Class[] { getDeploymentType() }, properties); | else | context = JAXBContext.newInstance(getDeploymentType()); | I think this should be extended to allow for passing in multiple types. I have a need for this as I use inheritance in my metadata and JAXB needs to be aware of all my types. It's either this, or force an upgrade to include to @XmlSeeAlso annotation that allows those types to be specified in the metadata itself. Note this issue is not with the JAXB.newInstance method but rather what the JAXBDeployer knows about (ie only discovered via the getDeploymentType() method). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029183#4029183 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029183

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Testsuite for MP1

by bill.burke＠jboss.com

Yes. I need advice on what I should be porting to work with the JBoss Test Harness and the new ESB Server. Just tests under qa/junit? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029154#4029154 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029154

19 years

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 March 2007