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

[Design of JBoss jBPM] - Re: how crucial are exception handlers ?

by camunda

In reality I don't like the use of exception handlers in the process too much. On the other hand is fault handling quite important in BPEL, so I think something comparable should be go into jPDL 4 too. So I think exception handlers are important for the language, because they are expected by the users... Even if I agree with you that it could be solved better by abstract base classes or the like. Cheers BErnd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132764#4132764 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132764

16 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by heiko.braun＠jboss.com

There is two issues that need to be addressed by the API: a) EJB MetaData access b) Invocation handling Back at JBW, we talked about solving the later by going through the MC bus: http://labs.jboss.com/file-access/default/members/jbossmc/freezone/docs/2... Andrew, can you confirm that an indirect MC invocation is equivalent to an invocation through the EJB container? The meta data piece is a deployment issue. WS requires access to the EJB meta data down to session and mdb meta data details. One idea was to use something similiar to Container.resolveAnnotation(...), however I see that this part has been deprecated. What's the replacement for it? I havn't spent much time on these issues lately, so any comments and ideas are welcome. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132748#4132748 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132748

16 years, 11 months

1
0
0 / 0

[Design of JMX on JBoss (JBoss/JMX)] - Re: JBAS-5220 - Twiddle not displaying Platform MBean.

by vickyk

[vicky@localhost bin]$ ./twiddle.sh query 'jboss.jca:*' | 13:56:16,758 ERROR [Twiddle] Exec failed | org.jboss.util.NestedRuntimeException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory; - nested throwable: (javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]) | at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:143) | at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:59) | at org.jboss.console.twiddle.command.MBeanServerCommand.queryMBeans(MBeanServerCommand.java:66) | at org.jboss.console.twiddle.command.QueryCommand.execute(QueryCommand.java:138) | at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305) | Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory] | at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657) | at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) | at javax.naming.InitialContext.init(InitialContext.java:223) | at javax.naming.InitialContext.<init>(InitialContext.java:175) | at org.jboss.console.twiddle.Twiddle.createMBeanServerConnection(Twiddle.java:235) | at org.jboss.console.twiddle.Twiddle.connect(Twiddle.java:268) | at org.jboss.console.twiddle.Twiddle.access$300(Twiddle.java:62) | at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:139) | ... 4 more | Caused by: java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory | at java.net.URLClassLoader$1.run(URLClassLoader.java:200) | at java.security.AccessController.doPrivileged(Native Method) | at java.net.URLClassLoader.findClass(URLClassLoader.java:188) | at java.lang.ClassLoader.loadClass(ClassLoader.java:306) | at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) | at java.lang.Class.forName0(Native Method) | at java.lang.Class.forName(Class.java:242) | at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42) | at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654) | ... 11 more | Twiddle seems to be broken on the truck , I just build the truck and am getting this exception . Can some one verify this ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132744#4132744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132744

16 years, 11 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Identity : no more JMX services for modules ?

by Antoine_h

Thanks a lot for these explaination, I have modified the start stop methods in my classes. good to know it will really be the only thing. I have seen the architecture is improving a lot ! very good job. thanks again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132743#4132743 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132743

16 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by heiko.braun＠jboss.com

anonymous wrote : I assume we still don't want to be using StatelessContainer directly. Right, that should covered by the WS-EJB API. But as long as EJB3 is in a state of flux I don't put my fingers on. I was going to wait until it consolidates and there's one codebase left. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132742#4132742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132742

16 years, 11 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - log4j in .sar file in jboss 4.0.4 GA

by girijasahoo

I have created a .sar file in JBoss. I want use log4j API. Should i use log4j.xml or log4j.properties ? Where to put the the log property file ? Can anyone help me ? Thanks in advance. Girija View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132736#4132736 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132736

16 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - jboss-ejb3-core in jbossas

by scott.stark＠jboss.org

I have jbossas/ejb3 just producing the ejb3.deployer using just the org/jboss/ejb3/deployers/** classes. The current jbossas projects using jboss-ejb3-core are: ejb3 - deployers embedded - org.jboss.ejb3.tx.TxUtil testsuite - org.jboss.ejb3.client.ClientLauncher tomcat - numerous inject related classes, org.jboss.ejb3.enc.DeploymentEjbResolver webservices - org.jboss.ejb3.BeanContext, org.jboss.ejb3.stateless.StatelessContainer, org.jboss.ejb3.Ejb3Deployment, etc. I'm working on the injection/resource resolution logic which will fix the tomcat dependencies. The webservices dependencies are the ones needing to be resolved with the ejb3/ws spi work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132735#4132735 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132735

16 years, 11 months

1
0
0 / 0

[Design of JBossCache] - High resource utilization on loading CMS portlet with HTML p

by suganthivelayutham

we are facing "High resource utilization on loading CMS portlet with HTML page in custom portal" for our application. In our portal, on accessing only a single page which has one CMS portlet is dropping the system entirely. Its found some dead lock of threads and cache memory which keeps on increasing in size thus soley utilizing full memory which is quite GB in size and 99% of CPU. Can anyone help with how JBOSS handles CMS loading at background and if any settings needs to be changed in JBOSS for custom Portals CMS. The only change done for CMSPortlet class is "path" is the file location of html page for the CMS instance got from preference | //TODO: To support multi lingual support we should take the locale issue fix from jboss. | // Commented the below code to handle the issue "Any content change from CMS Admin Portlet does | // not reflect in the custom portal cms portlet with out performating a server restart. | | /* | Command fileExistsCMD = CMSService.getCommandFactory().createItemExistsCommand(path + "/" + req.getLocale().getLanguage()); | Boolean bExists = (Boolean) CMSService.execute(fileExistsCMD); | | if(bExists.booleanValue()) | fileGetCMD = CMSService.getCommandFactory().createFileGetCommand(path, req.getLocale().getLanguage()); | else | fileGetCMD = CMSService.getCommandFactory().createFileGetCommand(path, new Locale(CMSService.getDefaultLocale())); | */ | fileGetCMD = CMSService.getCommandFactory().createFileGetCommand(path, new Locale(CMSService.getDefaultLocale())); | file = (File) CMSService.execute(fileGetCMD); Thanks in advance for guidance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132730#4132730 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132730

16 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by scott.stark＠jboss.org

The current org.jboss.wsf.container.jboss50.InvocationHandlerEJB3 that had the api issue is easily updated to use the org.jboss.wsf.container.StatelessContainer.localInvoke. With that change I have all of the jbossas trunk compiling against the external ejb3 artifacts. I assume we still don't want to be using StatelessContainer directly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132723#4132723 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132723

16 years, 11 months

1
0
0 / 0

[Design of POJO Server] - Re: Stats issue

by scott.stark＠jboss.org

Oh, ok. I thought that change was made a few revisions ago, but perhaps not. The issue was there were duplicate DeploymentTemplateInfo interfaces. It needs to be coming from the jboss-managed project, so org.jboss.managed.api.DeploymentTemplateInfo is the correct class. There is no org.jboss.deployers.spi.management.DeploymentTemplateInfo any longer, so the return value of getTemplate has changed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132718#4132718 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132718

16 years, 11 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-dev-forums February 2008