September 2008 - jboss-dev-forums

[Design the new POJO MicroContainer] - Re: virtualFile.toURL().openStream() does not provide a JarI

by alesj

"mstruk" wrote : Yes, I see it fail on Linux, but not on Windows. I get this on Windows as well. But only when running via mvn, but not in IDEA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175254#4175254 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175254

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: virtualFile.toURL().openStream() does not provide a JarI

by mstruk

Yes, I see it fail on Linux, but not on Windows. It's unrelated to this topic and looks like it's been around for a while (unnoticed by me :) Can JBVFS-57 be considered fixed? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175250#4175250 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175250

18 years

1
0
0 / 0

[Design of EJB 3.0] - Re: Which libraries for client?

by wolfc

Mr. Muhammad Ali, Please note that this forum is only for 'Design of EJB 3' discussions for developers and contributors. You may want to post your question to the 'EJB 3.0' forum here: http://www.jboss.com/index.html?module=bb&op=viewforum&f=221. Also please note that posts to that forum will be dealt with at the community's leisure. If your business is such that you need to rely on qualified answers within a known time frame, the forums might not be your preferred support channel. For professional support please go to JBoss Support Services: http://jboss.com/services/index With regards, Carlo de Wolf View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175242#4175242 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175242

18 years

1
0
0 / 0

[Design of EJB 3.0] - Re: Which libraries for client?

by smanaqvi83

Hello I am having the same problem in Seam Application. When hot deployment is done I got the following exception javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial | at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) | at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) | at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325) | at javax.naming.InitialContext.getNameParser(InitialContext.java:480) | at org.jboss.ejb3.NonSerializableFactory.unbind(NonSerializableFactory.java:60) | at org.jboss.ejb3.entity.PersistenceUnitDeployment.stop(PersistenceUnitDeployment.java:276) | 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:597) | at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.stop(Unknown Source) | at org.jboss.system.ServiceController.stop(ServiceController.java:508) | at sun.reflect.GeneratedMethodAccessor595.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy56.stop(Unknown Source) | at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175) | at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202) | at org.jboss.ejb3.Ejb3Deployment.stopPersistenceUnits(Ejb3Deployment.java:642) | at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:668) | at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.stop(Unknown Source) | at org.jboss.system.ServiceController.stop(ServiceController.java:508) | 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:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy33.stop(Unknown Source) | at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:532) | 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:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) | at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) | at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99) | 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:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy34.stop(Unknown Source) | at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667) | at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:659) | at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638) | at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632) | at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615) | 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:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | 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:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy9.undeploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.undeploy(URLDeploymentScanner.java:450) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:604) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) But this does not affect my application. Please give me solution ASAP. Bye Muhammad Ali View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175230#4175230 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175230

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: sar vs ear packaging

by thomas.diesler＠jboss.com

Alejandro, anonymous wrote : | The enterprise jar exposes the command service remotely, and the jms messaging / ejb scheduler services locally. If test cases were written in terms of commands (the EjbSchedulerTest actually is) then Cactus would not be needed. | | Nevertheless, the web console is not written in terms of commands because it is meant to work either standalone or in tandem with the enterprise jar. Because (a) it relies on the local functionality and (b) it is the only client provided with the distribution, it is not like any other client component. | ok, in that case the ear serves an actual purpose and we should stick to it. I'll take JBPM-1717 and do the ear as you suggested. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175228#4175228 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175228

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: sar vs ear packaging

by thomas.diesler＠jboss.com

Bernd, jBPM3 has a defined set of supported target containers. http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedTargetConta... For this we do QA for others we don't. To state that jBPM will work in arbitrary target containers is an assumption and we cannot base our packaging decisions on that. The support for various target containers is encapsulated in the installer. i.e. we install jbpm with the installer and QA that installation - no manual or hidden steps involved. Basically, if a feature is not automatically tested or not properly documented it is not there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175227#4175227 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175227

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: sar vs ear packaging

by camunda

I think the ear is a very convinient way for all people, starting with jBPM and don't knwo too much about deployment, sars & co. And as Tom mentioned, for everybody not using JBoss (which are quite some projects!) it is even more easy to start... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175222#4175222 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175222

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: simulation tests

by camunda

Hi Thomas, I will have a look at it as soon as possible, unfortunately a bit busy at the moment... As far as I remeber, the output was produced in DESMO-J and wasn't really configurable. So it may not be easy to get rid of it. But I am in touch with the university of Hamburg, where DESMO-J is developed, maybe we can improve DESMO-J "logging" somehow... As soon as I have more information on this I will let you know... Cheers Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175221#4175221 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175221

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by timfox

"clebert.suconic(a)jboss.com" wrote : | anonymous wrote : We need a super class we could reuse for other similar tests | | I mean... something that will start an INVM Transport, and a fake journal using FakeSequentialFiles (in memory) for quick tests. For most tests you can just use invm transport and null storage manager View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175217#4175217 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175217

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS4EE and AS5

by anil.saldhana＠jboss.com

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175196 has the discussion on this. This issue is resolved. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175197#4175197 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175197

18 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 September 2008