February 2008 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Request param acquire

by kooudy

sorry previous comment belongs to other thread View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128309#4128309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128309

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: WSSecureEndpoint and other security realm than JBossWS

by alessio.soldano＠jboss.com

"gllambi" wrote : "jason.greene(a)jboss.com" wrote : Yes, this value is hardocded by the webservices layer. We currently don't offer the ability for you to change this realm. However you could always request a feature enhancement on Jira if you would like support for this. http://jira.jboss.org | | | | -Jason | | If is true that you can't create domains in the context of WS-Security and EJB endpoints, could someone document it. I've been stucked with this problem for two days because I've created a realm. | | If I use JBossWS realm it works fine. Instead, the error I've got is a 401 not authorized. | | Thank you very much! | | Guzman Even if you actually can't change the realm name, you can of course use/define different security domains (@SecurityDomain("...")). If this is not enough for your usecase, feel free to create a jira feature request. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128308#4128308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128308

18 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Request param acquire

by kooudy

I have just discovered that: 1. redirect filter must be enabled to append parameters to URL 2. javax.faces.STATE_SAVING_METHOD must be set to client - according to BLOG example (when I tried to set to server, then it stops work) It is required to save state on client? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128307#4128307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128307

18 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Re: Request of Example of jBPM project

by kukeltje

Did you look at the jBPM examples in the source? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128306#4128306 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128306

18 years, 2 months

1
0
0 / 0

[EJB 3.0] - Re: Exception in MDB

by jybosse

Hi mwelss, Did you ever resolve your problem? I am facing a similar issue with the same version of JBoss (4.2.2 GA) and Jboss Messaging 1.4.0SP3 Thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128305#4128305 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128305

18 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Re: Seam and JBPM WebConsole

by kukeltje

anonymous wrote : Is it not included in the seam framework? No anonymous wrote : I tried to use the .war of this page | http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmWebConsole. | | It doesn't work. Correct, that is a version someone submitted once. The real webconsole is in the jBPM suite which you have to download View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128304#4128304 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128304

18 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Re: Jbpm tool to create xml from ProcessDefinition

by macd

i tried using JpdlXmlWriter from JBPM once. It worked creating a xml from a processdefinition read from a xml file. It didn't work creating an xml from a processdefinition read from my jbpmdatabase. AND it's deprecated.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128303#4128303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128303

18 years, 2 months

1
0
0 / 0

[JBossWS] - Re: http://org.jboss.ws/http#chunksize

by Ratoo

Just to keep this topic alive... Is there the possibility to fix it or should I use Metro stack instead? Thanx View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128301#4128301 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128301

18 years, 2 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - MDB implementing interface

by marcobaroetto

Hi, I get a deployment error error when i try to implement an interface from a MDB. This is my code: | public class MyConsumer implements MessageDrivenBean, MessageListener, MyInterface | And this is the exception: 11:58:17,919 WARN [ServiceController] Problem creating service jboss.j2ee:ear=MyMDBEar.ear,jar=MyMDB.jar,name=MyConsumer,service=EJB3 | java.lang.RuntimeException: An exception occurred initialising interceptors for class it.mypack.mdb.MyConsumer.onMessage | at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.createPerJoinpoint(EJB3InterceptorsFactory.java:108) | at org.jboss.aop.advice.AspectFactoryDelegator.createPerJoinpoint(AspectFactoryDelegator.java:119) | at org.jboss.aop.advice.ScopedInterceptorFactory.create(ScopedInterceptorFactory.java:113) | at org.jboss.aop.Advisor.createInterceptorChain(Advisor.java:618) | at org.jboss.aop.Advisor.pointcutResolved(Advisor.java:888) | at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:650) | at org.jboss.aop.ClassContainer.createInterceptorChains(ClassContainer.java:248) | at org.jboss.aop.ClassContainer.rebuildInterceptors(ClassContainer.java:115) | at org.jboss.aop.ClassContainer.initializeClassContainer(ClassContainer.java:58) | at org.jboss.ejb3.EJBContainer.create(EJBContainer.java:548) | 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.ejb3.ServiceDelegateWrapper.createService(ServiceDelegateWrapper.java:87) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) | 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.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.create(Unknown Source) | at org.jboss.system.ServiceController.create(ServiceController.java:330) | at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | 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 $Proxy138.create(Unknown Source) | at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:119) | at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:301) | at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:362) | at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | 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.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.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | 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.start(Unknown Source) | at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512) | 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.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.start(DeployerInterceptor.java:87) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | 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.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | 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.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) | 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) | Caused by: java.lang.RuntimeException: unable to determine messagingType interface for MDB | at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:88) | at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.getBusinessInterfaces(EJB3InterceptorsFactory.java:167) | at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.isBusinessMethod(EJB3InterceptorsFactory.java:122) | at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.createPerJoinpoint(EJB3InterceptorsFactory.java:98) | ... 108 more Any hint? Thanx View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128300#4128300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128300

18 years, 2 months

1
0
0 / 0

[Beginners Corner] - Re: fileupload

by mars1412

"PeterJ" wrote : What mechanism are you using for the file download? you mean upload, do you? "PeterJ" wrote : If I recall correctly, the apache commons file upload library provides a mechanism to query the file size before uploading the file. well - my question is a more general one - not related to any library I know, the apache commons file upload has a way to limit the upload size. and also the seam s:fileUpload tag has such a setting. but I am wondering if those settings are making any difference, because the client will always build the request and send the complete very large request to the server (consuming bandwidth), and if the server must process the complete very large request, before it knows that the file is too large, it will also consume a lot of memory and CPU. I guess that this is the case, because the filesize is not included in any meta-data information. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128299#4128299 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128299

18 years, 2 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-user February 2008