August 2008 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: Looking at deployment structure - JBAS-5823

by scott.stark＠jboss.org

I think the DeploymentManager.distribute(String name, DeploymentPhase phase, URL contentURL) should become: distribute(String name, DeploymentPhase phase, URL contentURL, boolean copyContent); and DeploymentTarget.distribute(DeploymentID deployment) should become: DeploymentTarget.distribute(DeploymentID deployment, boolean copyContent) The StreamingDeploymentTarget.distribute would then either pass in the stream or just the url via another distribute(DeploymentID) method that would be added to the org.jboss.profileservice.management.upload.remoting.DeployHandler.invoke(InvocationRequest) else clause: | else | { | Map payload = request.getRequestPayload(); | DeploymentID dtID = (DeploymentID) payload.get("DeploymentTargetID"); | log.debug("invoke, payload: "+payload+", parameter: "+parameter); | if( parameter.equals("distribute")) | { | DeploymentPhase phase = (DeploymentPhase) payload.get("phase"); | returnValue = distribute(dtID, phase); | } | else if( parameter.equals("getRepositoryNames")) | { | String[] names = (String[]) payload.get("names"); | DeploymentPhase phase = (DeploymentPhase) payload.get("phase"); | returnValue = getRepositoryNames(names, phase); | } | else if( parameter.equals("start") ) | { | start(dtID); | } | else if( parameter.equals("stop") ) | { | stop(dtID); | } | else if( parameter.equals("undeploy") ) | { | undeploy(dtID); | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171400#4171400 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171400

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Added Netty transport to the trunk

by clebert.suconic＠jboss.com

I have once played with changing how the buffers are created on JBM 2, and I'm sure we don't need auto-expanding buffers. When we send a message, we could verify the getEncodeSize(), and pre-allocate the buffers at the exact size necessary to send them. It shouldn't be too difficult of doing that. So, if you (Trustin) are having issues with the auto-expanding buffer, I'm pretty sure we can get rid of that. (At least on sending.. I'm not sure how the buffers are created on reading). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171387#4171387 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171387

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Looking at deployment structure - JBAS-5823

by alesj

"scott.stark(a)jboss.org" wrote : The SerializableDeploymentID representing the deployment has a contentURL that could be used to represent the old style of external deployment that could be added via reference rather than by copy. | So, how to diff between what PS does now and what we used to do? New method? Leaving distribute to do current stream copy, where reference/xyz would do the old ref style? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171377#4171377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171377

17 years, 7 months

1
0
0 / 0

(no subject)

by Sergio Stateri Jr

How can I set the HTTP timeout of JBoss 4.2.2 GA ? I´d like to set the time that HTTP server (not the Servlet container) will wait to return a HTTP timeout page (it´s not the session-timeout of web.xml file). thanks in advance, Sergio Stateri Jr. Sergio.stateri(a)accurate.com.br

17 years, 7 months

1
0
0 / 0

[Design of Management Features on JBoss] - JBAS-5862: New look for jmx-console

by csaldanh

Hi I have attached a patch to JBAS-5862 along with a zip file for people to try it out. Cheers Clive https://jira.jboss.org/jira/browse/JBAS-5862 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171363#4171363 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171363

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Using AnnotationEnvironment in Seam

by epbernard

I am not sure where we will get the speed improvement but if it's by limiting the amount of classes we scan manually, the we probably need: - Getting classes/method/ctrs annotated with meta annotations is useful. - Getting intersections of annotated classes too: get all class with @Named and @Startup, could be useful too (not entirely sure but I can see a couple of use cases) - Getting a class hierarchy: its often that you need to build a class hierarchy based on a given class, might be useful as a service? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171359#4171359 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171359

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Build failed message

by clebert.suconic＠jboss.com

anonymous wrote : I'd recommend applying the change consistently across all test suites I'm not sure if we should do that... a failing unit-test will abort the build... When you run all-tests, you want the entire testsuite to run, even if you have a failure on an integration test for example. Applying the same logic would cancel the build. We talked about that when I first committed this. We could of course change it to just show a "Build Failed" at the end, but that's not an easy thing to do with ant due to how the variables work on ant. (each ant-target call will initialize a new method.. you won't have a global variable where you could change). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171349#4171349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171349

17 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: bundling JTS into AS 5.0

by scott.stark＠jboss.org

I think that is the best approach for now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171346#4171346 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171346

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Paging discussion:

by clebert.suconic＠jboss.com

anonymous wrote : Yes, the message can maintain a durable count and a non durable count, but you can use the same methods for incrementing / decrementing. I would need a parameter on increment / decrement to determine if it is durable or not. The ServerMessage don't know about that Besides based on where the calls are made it is easier to keep two separate methods for each increment and decrement. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171345#4171345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171345

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - vfsmemory url problem

by scott.stark＠jboss.org

One of the appclient jbossas test regressions is due to the following error resulting from a vfs url of the form: vfsmemory://5c4o0b-m9hkak-fk2sx83e-1-fk2t2t85-1z/classes/ | 2265 [main] WARN org.jboss.kernel.plugins.dependency.AbstractKernelController - Broken callback: ClassSingleCallbackItem@563a3d{name=class org.jboss.classloading.spi.dependency.Module whenRequired=ControllerState@7e33de{Configured} dependentState=ControllerState@7f4790{Installed} attributeName=addModule owner=AbstractKernelControllerContext@6f84d8{ metadata=AbstractBeanMetaData@5e8a8f{name=ClassLoading bean=org.jboss.classloading.spi.dependency.ClassLoading properties= constructor=null autowireCandidate=true installCallbacks=[method=addModule] uninstallCallbacks=[method=removeModule]}name=ClassLoading target=org.jboss.classloading.spi.dependency.ClassLoading@f6e3e9 state=Installed depends=AbstractDependencyInfo@335332{idependOn=[]}} signature=org.jboss.classloading.spi.dependency.Module} | java.lang.IllegalArgumentException: Root can not contain '/' | at org.jboss.virtual.plugins.context.memory.MemoryContextFactory.createRoot(MemoryContextFactory.java:108) | at org.jboss.virtual.plugins.context.memory.MemoryContextFactory.getVFS(MemoryContextFactory.java:76) | at org.jboss.virtual.VFS.getVFS(VFS.java:89) | at org.jboss.virtual.VFS.getRoot(VFS.java:103) | at org.jboss.classloading.spi.vfs.dependency.VFSClassLoaderPolicyModule.determineVFSRoots(VFSClassLoaderPolicyModule.java:170) | at org.jboss.classloading.spi.vfs.dependency.VFSClassLoaderPolicyModule.determineCapabilities(VFSClassLoaderPolicyModule.java:98) | at org.jboss.classloading.spi.dependency.Module.getCapabilities(Module.java:485) | at org.jboss.classloading.spi.dependency.Module.determinePackageNames(Module.java:544) | at org.jboss.classloading.spi.dependency.ClassLoadingSpace.join(ClassLoadingSpace.java:213) | at org.jboss.classloading.spi.dependency.Domain.addModule(Domain.java:151) | at org.jboss.classloading.spi.dependency.ClassLoading.addModule(ClassLoading.java:58) | 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.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59) | at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150) | at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) | at org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300) | at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:279) | at org.jboss.dependency.plugins.SingleCallbackItem.changeCallback(SingleCallbackItem.java:67) | at org.jboss.dependency.plugins.AbstractCallbackItem.changeCallback(AbstractCallbackItem.java:79) | at org.jboss.dependency.plugins.OwnerCallbackItem.changeCallback(OwnerCallbackItem.java:88) | at org.jboss.dependency.plugins.AbstractController.resolveCallbacks(AbstractController.java:1398) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:908) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1026) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:948) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:738) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:506) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:331) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:309) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130) | at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:76) | at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:88) | at org.jboss.ejb3.client.ClientLauncher.deploy(ClientLauncher.java:349) | at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:241) | at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:158) | at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:147) | at org.jboss.test.ee5client.unit.SimpleResourceUnitTestCase.testClientLauncher(SimpleResourceUnitTestCase.java:100) | The appclient is not creating this url, so I'm not sure where its coming from or why this is an invalid vfsmemory url. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171344#4171344 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171344

17 years, 7 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 August 2008