April 2009 - jboss-user - Jboss List Archives

[JBoss OSGi] - Re: Access OSGIFramework from Stateless

by thomas.diesler＠jboss.com

Please monitor https://jira.jboss.org/jira/browse/JBOSGI-58 Can you see the framework in the jmx-console? Can you inject other MBeans? The MBean that we currently bind to JMX is ManagedFrameworkMBean and not OSGiFramework But you are right the OSGiFramework should be injectable. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223201#4223201 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223201

15 years, 9 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: What's the best way to package utility jars in exploded

by bdt＠star.be

mikemil, In the mean time, the EJB spec has included a portable solution to this problem. JBoss 4.2.x is compatible with this new standard. Just put your jars in your.ear/lib It is a bit like putting jars in yourapp.war/WEB-INF/lib except that they are loaded in the class loader of the ear. You will find more info googling. Bernard View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223198#4223198 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223198

15 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: NullPointerException in JavaEEComponentHelper with JBoss

by jaikiran

anonymous wrote : Caused by: java.lang.NullPointerException | at org.jboss.ejb3.javaee.JavaEEComponentHelper.createObjectName(JavaEECo | mponentHelper.java:46) | at org.jboss.ejb3.deployers.JBoss5DeploymentScope.getEjbContainer(JBoss5 | DeploymentScope.java:170) | at org.jboss.ejb3.Ejb3Deployment.getEjbContainer(Ejb3Deployment.java:410 | ) | at org.jboss.ejb3.EJBContainer.resolveEjbContainer(EJBContainer.java:141 | 8) | at org.jboss.injection.AbstractHandler.addDependency(AbstractHandler.jav | a:50) | at org.jboss.injection.EJBRemoteHandler.ejbRefDependency(EJBRemoteHandle | r.java:146) | at org.jboss.injection.EJBRemoteHandler.handleFieldAnnotations(EJBRemote | Handler.java:393) | at org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUt | il.java:160) | at org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.ja | va:197) | at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:590) | at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deploym | Hmmm, do you have a bean which is having a @EJB to inject another bean? And do these two beans reside in two separate jar files? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223195#4223195 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223195

15 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: NullPointerException in JavaEEComponentHelper with JBoss

by jaikiran

Could you please explain a bit more about your application packaging? What does the EAR contain? Post the output of jar -tf ifsapp.ear Also do you have a application.xml? If yes, please post its contents. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223194#4223194 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223194

15 years, 9 months

1
0
0 / 0

[Microcontainer] - Re: More trouble in the bean-deployer schema

by alex.loubyansky＠jboss.com

The parsing error seems to be clear enough? There is no bean in the schema type for parameter, hence it can't appear there. As to the schema validation errors, the group appears to be not properly redefined. The way it's redefined is supposed to be a restriction, i.e. you should list a subset of the elements/groups of the group you are redefining. If you want extension, you should reference the group you are redefining in the new group and add the elements you want. Looking at the schemas, the groups are identical in both schemas (with bean element commented out, btw). So, you can just remove the group as a child of redefine. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223191#4223191 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223191

15 years, 9 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - maxPostSize parameter on HTTP connector

by tmoosa

Hi guys, Let me start off with some background information. I have developed some web services using the Documentum foundation services sdk and deployed them to a JBoss 4.2.2 application server. I expose these services on the standard HTTP port and all sorts of security and authentication is handled by the application and not the web server. I have a requirement to restrict incoming messages to 5 MB. I do not want to handle this functionality in my application but rather have it sorted out on the server side for obvious architectural reasons. I have been investigating how this can be done on JBoss 4.2.2 and I was lead to believe that adding the maxPostSize parameter on the HTTP connector would solve my problem but unfortunately it does not seem to work. I added this parameter to the relevant file, and then changed the attribute value but constantly used a 5MB as a test case. The server did not throw any exceptions and adding this parameter does not seem to work. Could you please assist me with getting this working??? The JBoss documentation gives the following description for the maxPostSize parameter: anonymous wrote : The maximum size in bytes of the POST which will | be handled by the container FORM URL parameter | parsing. The limit can be disabled by setting this attribute | to a value less than or equal to 0. If not specified, | this attribute is set to 2097152 (2 megabytes). I have read this almost a thousand times and the only section that seems to be vague is : anonymous wrote : ...handled by the container FORM URL parameter | parsing... Am I on the right track to finding a solution or is there some other way to restrict large input message. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223189#4223189 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223189

15 years, 9 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: How to Disable Caching in Jboss AS 5.0.1 Default Server?

by jaikiran

"bsgcic" wrote : I am not sure which caching it is. Whatever jboss 5.0.1.GA uses as its caching for the default server out of the box. It appears that the project is cached in jboss-5.0.1.GA\server\default\tmp | Let me ask this in a different way - Is this caching (wherever it's happening) affecting your application? If yes, how? Explain a bit more about your application and the caching that you are seeing, maybe that will give us some hint. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223185#4223185 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223185

15 years, 9 months

1
0
0 / 0

[EJB 3.0] - NullPointerException in JavaEEComponentHelper with JBoss-5.1

by japase

Hi, Our EJB3 application deploys without problems in JBoss 4.3, but in 5.x I get NullPointerException in JavaEEComponentHelper. I've started my tests in JBoss 5.0.1GA (jdk6) and got this problem, so after some googling I found a thread describing a similar problem in previous version of JBoss (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=138480) and related JIRA (https://jira.jboss.org/jira/browse/JBAS-5713) stated that the problem has been resolved in JBoss 5.1.0.Beta1. So I've downloaded this version (also jdk6), but the problem is still there. | 08:15:31,758 ERROR [AbstractKernelController] Error installing to Real: name=vfs | file:/E:/ifs_home_WS/jboss-5.1.0.Beta1/server/dev/deploy/ifsapp.ear/ state=PreRe | al mode=Manual requiredState=Real | org.jboss.deployers.spi.DeploymentException: Error deploying administrateuserpro | files-ejb.jar: null | at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:196) | at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:99) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internal | Deploy(AbstractVFSRealDeployer.java:45) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy( | AbstractRealDeployer.java:50) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(Deployer | Wrapper.java:171) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(Deployer | sImpl.java:1439) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFi | rst(DeployersImpl.java:1157) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFi | rst(DeployersImpl.java:1210) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(Deployers | Impl.java:1098) | at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra | ctControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractContr | oller.java:1598) | at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra | ctController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr | actController.java:1062) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr | actController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractContro | ller.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractContro | ller.java:553) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(Deployers | Impl.java:781) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeploye | rImpl.java:698) | at org.jboss.system.server.profileservice.repository.MainDeployerAdapter | .process(MainDeployerAdapter.java:117) | at org.jboss.system.server.profileservice.repository.ProfileDeployAction | .install(ProfileDeployAction.java:59) | at org.jboss.system.server.profileservice.repository.AbstractProfileActi | on.install(AbstractProfileAction.java:53) | at org.jboss.system.server.profileservice.repository.AbstractProfileServ | ice.install(AbstractProfileService.java:355) | at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra | ctControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractContr | oller.java:1598) | at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra | ctController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr | actController.java:1062) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr | actController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractContro | ller.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractContro | ller.java:553) | at org.jboss.system.server.profileservice.repository.AbstractProfileServ | ice.activateProfile(AbstractProfileService.java:310) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start( | ProfileServiceBootstrap.java:241) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java: | 461) | at org.jboss.Main.boot(Main.java:216) | at org.jboss.Main$1.run(Main.java:546) | at java.lang.Thread.run(Thread.java:619) | Caused by: java.lang.NullPointerException | at org.jboss.ejb3.javaee.JavaEEComponentHelper.createObjectName(JavaEECo | mponentHelper.java:46) | at org.jboss.ejb3.deployers.JBoss5DeploymentScope.getEjbContainer(JBoss5 | DeploymentScope.java:170) | at org.jboss.ejb3.Ejb3Deployment.getEjbContainer(Ejb3Deployment.java:410 | ) | at org.jboss.ejb3.EJBContainer.resolveEjbContainer(EJBContainer.java:141 | 8) | at org.jboss.injection.AbstractHandler.addDependency(AbstractHandler.jav | a:50) | at org.jboss.injection.EJBRemoteHandler.ejbRefDependency(EJBRemoteHandle | r.java:146) | at org.jboss.injection.EJBRemoteHandler.handleFieldAnnotations(EJBRemote | Handler.java:393) | at org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUt | il.java:160) | at org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.ja | va:197) | at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:590) | at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deploym | ent.java:418) | at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:526) | at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:189) | ... 34 more | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223177#4223177 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223177

15 years, 9 months

1
0
0 / 0

[JBoss Messaging] - Re: Messaging blocked by long time-out again

by timfox

"lanceliao1" wrote : | The remoting guys resolve the problem by setting TCP TTL.This is a ugly way. JBM 1.x uses JBoss Remoting 2.x, all the transport stuff is handled by JBR so it's up to the JBR team to fix issues related to tha. FWIW JBM 2.0 does not use JBoss Remoting at all, it uses Netty. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223175#4223175 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223175

15 years, 9 months

1
0
0 / 0

[JBoss Tools (users)] - Re: Seam Components Problem

by max.andersen＠jboss.com

Sorry you are having problems. I can see you are using CR1 we have had CR2 and GA since then. Could you try a later version and then let us know if it is still a problem ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223173#4223173 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223173

15 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user April 2009