September 2006 - jboss-dev-forums

[Design of JBoss Portal] - Re: Portal security implementation now abstracted from JACC

by rui.cunha

I, thanks for this post. It help a lot, but i'm getting a little problem. I'm using it to check if I have access to a portal page. But i'm only getting permission if the permissions to that page is checked as Uncheck, if i choose one role that the user belongs to it, return false. I also tried the way that is described in the Chapter 5 of the Jboss Portal 2.2, and the result is the same. I think that the PortalSubject that it uses is not the user that i'm using, for some reason that i can't understand. Do i need to do something before or the portal should know how is the user that is looged in? I'm using JBoss AS 4.0.3SP1 and Jboss Portal 2.2. Thanks in advance Rui Cunha View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971958#3971958 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971958

19 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: MessageService and JMS

by koen.aers＠jboss.com

Manuel, There were all kinds of problems with the integration of the GPD and the jBPM HEAD branch. We managed to do this integration today though and it should go fine now. Let us definitely know if you have any problems... Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971950#3971950 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971950

19 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: MessageService and JMS

by tom.baeyens＠jboss.com

finally we managed to build the suite again. clean your local repository directory jbpm (mainly the designer) then do a build/build.xml clean and a jpdl/dist/build.xml package. that will generate a new distribution a la starters kit (now called suite). so the designer problem should be fixed if you install a clean fresh build of the designer (from src). it's strange that we don't have this .ear deployment problem... Also i use the 4.0.4.GA. in the jboss/configuration/build.xml, there are also targets to install a fresh jboss (4.0.4.GA) from the files in the local repository. see if you can build a fresh jboss installation and configuration by only using these targets and making sure that you create the new jboss installation in a clean location. that should make it reproducable. (unless there is a windows/linux difference) please keep us posted. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971947#3971947 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971947

19 years, 6 months

1
0
0 / 0

[Design of JBossCache] - Re: Runtime changes of cache config elements

by manik.surtani＠jboss.com

This just seems like a mechanism of how I would expose setters to allow mutation of certain configs via JMX or the profile service. The purpose of this thread is more to talk about *how* I plan to enforce such mutability internally (since programmatically someone can still get a hold of the Configuration object and change it), as well as a discussion on which elements should be mutable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971944#3971944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971944

19 years, 6 months

1
0
0 / 0

[Design of JBoss Serialization] - Re: Debug support for Serialization

by clebert.suconic＠jboss.com

You probably has a non serializable class, without a default constructor in your object's graph. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971925#3971925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971925

19 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1115 - Automatic detection of Tomcat port

by darran.lofthouse＠jboss.com

Quite often users are requesting the ability to automatically set the port to be used for WSDL generation / URL replacement. I would like to add something to 'ServerConfigImpl' to query all of the Tomcat connectors currently registered with the MBean server. Take the first connector with scheme 'http' and secure set to false as the webServicePort. Take the first connector with scheme 'http' and secure set to true as the webServiceSecurePort. If multiple connectors are found a warning can be logged. The values can then be injected into the ServiceEndpointManager. The majority of users appear to have a problem when they are changing the Tomcat port or using the binding manager, this implementation would cover this. For users with advanced use cases they can still modify the jboss-beans.xml as before. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971921#3971921 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971921

19 years, 6 months

1
0
0 / 0

[Design of JBoss Serialization] - Re: Debug support for Serialization

by hmesha

Have you been able to find out the root cause of this issue? I'm seeing the same exception thrown using JBossAS 4.0.5CR1. I'd like to find out if there's a solution or known bug to this before I start digging in the code. Thanks, Hany View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971917#3971917 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971917

19 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1205 - Temporary files created parsing WSDL

by darran.lofthouse＠jboss.com

When the WSDL is parsed a number of temporary files are created under 'server\default\tmp\jbossws', this is not a problem for deployments but for clients that regularly lookup remote services each invocation causes new files to be added. I would like to modify WSDL11Reader to delete all temporary files created as part of the parsing process once parsing is complete instead of setting 'deleteOnExit'. Running the testsuite this does not cause any failures, I just wanted to check if anyone knew of any reasons why this files may be needed to be kept? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971914#3971914 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971914

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Common JBossMQ/JBossMessaging testsuite

by dimitris＠jboss.org

Is there already, or is it planned to have a common testsuite between the old and the new messaging, based on Adrian's JBossAdmin abstraction (when he integrated the JORAM testsuite) ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971910#3971910 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971910

19 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: MessageService and JMS

by mteira

About the problem deploying in JBoss 4.0.4 GA the jbpm.ear with the provided application.xml , it was: 12:41:54,945 INFO [EARDeployer] Init J2EE application: file:/opt/jboss/server/oracluster/deploy/jbpm.ear | 12:41:54,972 ERROR [MainDeployer] Could not initialise deployment: file:/opt/jboss/server/oracluster/deploy/jbpm.ear | org.jboss.deployment.DeploymentException: Invalid module content, must be one of: ejb, web, java, connector, service, har, | at org.jboss.deployment.J2eeModuleMetaData.importXml(J2eeModuleMetaData.java:166) | at org.jboss.deployment.J2eeModuleMetaData.importXml(J2eeModuleMetaData.java:107) | at org.jboss.deployment.J2eeApplicationMetaData.importApplicationXml(J2eeApplicationMetaData.java:178) | at org.jboss.deployment.J2eeApplicationMetaData.importXml(J2eeApplicationMetaData.java:139) | at org.jboss.deployment.EARDeployer.init(EARDeployer.java:141) | at org.jboss.deployment.MainDeployer.init(MainDeployer.java:861) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:798) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at sun.reflect.GeneratedMethodAccessor10.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 $Proxy6.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) | 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.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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755) | 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.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 $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:464) | at java.lang.Thread.run(Thread.java:595) | 12:41:54,986 ERROR [URLDeploymentScanner] Incomplete Deployment listing: | | --- Incompletely deployed packages --- | org.jboss.deployment.DeploymentInfo@4e9bcc36 { url=file:/opt/jboss/server/oracluster/deploy/jbpm.ear } | deployer: org.jboss.deployment.EARDeployer@9c2715 | status: null | state: FAILED | watch: file:/opt/jboss/server/oracluster/deploy/jbpm.ear | altDD: null | lastDeployed: 1158316914971 | lastModified: 1158316914000 | mbeans: And that's why I changed it to a web tag with its context-root. Any idea about my problem with the designer compressed site? Is it missing something? Thanks a lot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971899#3971899 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971899

19 years, 6 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 September 2006