[Persistence, JBoss/CMP, Hibernate, Database] - Re: Jboss Server Crashed ! ! !
by PeterJ
You cannot go by the memory sizes given by ps. In other words, if you add up the memory used by all processes the sum will be much larger than the actual amount of memory used, mainly because any shared libraries and shared memory areas appear physically only once in memory but are listed for each process that uses them. For a detailed explanation, see http://virtualthreads.blogspot.com/2006/02/understanding-memory-usage-on-...
And because of the threading model you are using, each thread for the java processes running JBossAS will show the same memory, so it looks like a lot more memory being used than what it really is.
Finally, it is typical for an application server to have dozens of threads when it first starts, and then grow to hundreds of threads as it gets busy. With your threading model, you will end up with hundreds on process entries.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178871#4178871
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178871
17 years, 7 months
[JBoss jBPM] - jPDL: variable participants and parallel processes
by r1ch4rd
Hi Folks,
I'm new to jBPM and jPDL, and am trying to design a workflow with a particular feature which I can't see how to implement in jPDL. This is easiest to explain by example, so this is what I'm trying to do:
I have a workflow which takes a list of users as an input; the number of users is unknown before the workflow is initiated. For each of this variable number of participants I want an author/reject/approve set of stages where the participant creates some content and a manager rejects it (sending it back to the participant for changes) or approves it. I want each user to be totally independent during this cycle, so that while one's content is in an approve stage, another's content can still be in the authoring stage.
I have achieved this using jPDL up to the point that I have an author/reject/approve set of stages for ALL users, but in the application I am using to run this workflow (Daisy), only deals with task pools, not tasks for multiple independent actors. I dove into the source code, and found the interface in jBPM for Assignable, and this appears to be aimed at either individual users or task pools also. Can I read into this that the behaviour I'm looking for is not possible in jBPM/jPDL?
The root of my question is: is there any way, in jPDL, to define a workflow pattern (author/reject/approve) which can be, in a running instance of a larger workflow, copied into multiple parallel instances of that pattern, such that a variable number of actors can participate in the same bit of workflow but independently from eachother. OR ... is this something which applications using jBPM need to implement, by hijacking the Assignable.setPooledActors() for an alternative purpose?
Any help would be greatly appreciated; I'm totally at a loss as to whether this is even possible right now!
Thanks in advance,
Richard
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178867#4178867
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178867
17 years, 7 months
[EJB/JBoss] - Re: How To Modify Global JNDI Name
by Crucifix
This is exactly what I wanted. Thanks so much for your help!
I see I no longer need to specify the 'name' in the @Stateless attribute either. This is my Global JNDI Namespace before and after the change:
Before:
| @Stateless(name="TestEJB")
| @Remote(IPing.class)
|
| +- TestEAR-1.0.0 (class: org.jnp.interfaces.NamingContext)
| | +- TestEJB (class: org.jnp.interfaces.NamingContext)
| | | +- remote (proxy: $Proxy161 implements interface test.IPing,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
|
After:
| @Stateless
| @Remote(IPing.class)
| @RemoteBinding(jndiBinding="TestEAR/TestEJB/remote")
|
| +- TestEAR (class: org.jnp.interfaces.NamingContext)
| | +- TestEJB (class: org.jnp.interfaces.NamingContext)
| | | +- remote (proxy: $Proxy177 implements interface test.Ping,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178865#4178865
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178865
17 years, 7 months
[Installation, Configuration & DEPLOYMENT] - Configuring JBoss 5.0.0 CR1 for MySQL
by mayankmit2002
Hi All,
I would like to use JBoss 5.0.0 for my development with MySql5.1, but when on configuring the server I got following error:
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: E:\jboss-5.0.0.CR1
JAVA: c:\program files\java\jdk1.6.0_10\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: E:\jboss-5.0.0.CR1\bin\run.jar
===============================================================================
21:24:32,618 INFO [ServerImpl] Starting JBoss (Microcontainer)...
21:24:32,618 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200806301254)
21:24:32,618 INFO [ServerImpl] Home Dir: E:\jboss-5.0.0.CR1
21:24:32,618 INFO [ServerImpl] Home URL: file:/E:/jboss-5.0.0.CR1/
21:24:32,618 INFO [ServerImpl] Library URL: file:/E:/jboss-5.0.0.CR1/lib/
21:24:32,618 INFO [ServerImpl] Patch URL: null
21:24:32,618 INFO [ServerImpl] Server Name: default
21:24:32,618 INFO [ServerImpl] Server Home Dir: E:\jboss-5.0.0.CR1\server\default
21:24:32,618 INFO [ServerImpl] Server Home URL: file:/E:/jboss-5.0.0.CR1/server/default/
21:24:32,618 INFO [ServerImpl] Server Data Dir: E:\jboss-5.0.0.CR1\server\default\data
21:24:32,618 INFO [ServerImpl] Server Temp Dir: E:\jboss-5.0.0.CR1\server\default\tmp
21:24:32,868 INFO [ServerImpl] Server Config URL: file:/E:/jboss-5.0.0.CR1/server/default/conf/
21:24:32,868 INFO [ServerImpl] Server Library URL: file:/E:/jboss-5.0.0.CR1/server/default/lib/
21:24:32,868 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
21:24:33,930 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/E:/jboss-5.0.0.CR1/server/default/conf/bootstrap.xml
21:24:35,288 INFO [CopyMechanism] VFS temp dir: E:\jboss-5.0.0.CR1\server\default\tmp
21:24:35,304 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
21:24:40,658 INFO [ServerInfo] Java version: 1.6.0_10-beta,Sun Microsystems Inc.
21:24:40,658 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 11.0-b11,Sun Microsystems Inc.
21:24:40,658 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
21:24:41,174 INFO [JMXKernel] Legacy JMX core initialized
21:24:43,469 INFO [MetaDataAwareProfile] Using profile root:E:\jboss-5.0.0.CR1\server\default
21:24:48,480 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
21:25:09,478 WARN [HackClassloaderMetaDataDeployer] FIXME Using loader repository config: jboss.console:sar=console-mgr.sar for vfsfile:/E:/jboss-5.0.0.CR1/server/default/deploy/management/console-mgr.sar/ use classloading metadata not loader repository config
21:25:10,680 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@144f47b for BaseClassLoader@977e69{vfsfile:/E:/jboss-5.0.0.CR1/server/default/deploy/ejb3-interceptors-aop.xml}
21:26:20,161 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
21:26:20,489 INFO [MailService] Mail Service bound to java:/Mail
21:26:20,598 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instru
ctions on how to do this.
21:26:21,770 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
21:26:21,770 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
21:26:22,598 INFO [TransactionManagerService] Starting recovery manager
21:26:23,035 INFO [TransactionManagerService] Recovery manager started
21:26:23,035 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
21:26:24,269 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: c:\program files\java\jdk1.6.0_10\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS
;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\ULTRAE~1;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\CVSNT\;C:\Program Files\Java\jdk1.6.0_10\bin
21:26:24,394 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
21:26:24,410 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
21:26:24,410 INFO [Catalina] Initialization processed in 1003 ms
21:26:24,410 INFO [StandardService] Starting service jboss.web
21:26:24,410 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.CR3
21:26:24,535 INFO [Catalina] Server startup in 130 ms
21:26:25,004 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.0.CR1/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
21:26:25,035 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.0.CR1/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
21:26:25,066 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.0.CR1/server/default/deploy/jms-ra.rar/META-INF/ra.xml
21:26:25,097 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.0.CR1/server/default/deploy/mail-ra.rar/META-INF/ra.xml
21:26:25,144 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.0.CR1/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
21:26:25,379 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
21:26:25,457 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
21:26:25,457 INFO [RAMJobStore] RAMJobStore initialized.
21:26:25,457 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
21:26:25,457 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
21:26:25,472 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
21:26:26,066 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
21:26:26,066 INFO [NativeServerConfig] 3.0.2.GA
21:26:28,862 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
21:26:29,924 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
21:26:30,034 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
21:26:30,127 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war
21:26:30,330 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
21:26:31,393 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
21:26:32,861 WARN [JDBCPersistenceManager]
JBoss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently REPEATABLE_READ.
Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems.
Using an isolation level more strict than READ_COMMITTED may lead to deadlock.
21:26:33,049 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE QRTZ_JOB_DETAILS(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL, DESCRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE VARCHAR(1) NOT NULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VA
RCHAR(1) NOT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))
21:26:33,174 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
21:26:33,174 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
21:26:33,174 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
21:26:33,189 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
21:26:33,189 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
21:26:33,205 INFO [JobStoreCMT] JobStoreCMT initialized.
21:26:33,205 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
21:26:33,205 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
21:26:33,205 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
21:26:33,205 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
21:26:33,205 INFO [JobStoreCMT] Recovery complete.
21:26:33,205 INFO [JobStoreCMT] Removed 0 'complete' triggers.
21:26:33,205 INFO [JobStoreCMT] Removed 0 stale fired job entries.
21:26:33,236 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
21:26:33,689 INFO [ServerPeer] JBoss Messaging 1.4.1.CR1 server [0] started
21:26:33,752 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
21:26:33,986 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging.connectionfactory:service=ConnectionFactory
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging.destination:name=DLQ,service=Queue
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging.destination:name=ExpiryQueue,service=Queue
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging:service=PostOffice
-> jboss.jgroups:service=ChannelFactory{Create:** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory **}
*** CONTEXTS IN ERROR: Name -> Error
jboss.jgroups:service=ChannelFactory -> ** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory **
21:26:34,017 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
21:26:34,048 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
21:26:34,064 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200806301254)] Started in 2m:1s:196ms
21:26:34,626 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging.connectionfactory:service=ConnectionFactory
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging.destination:name=DLQ,service=Queue
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging.destination:name=ExpiryQueue,service=Queue
-> jboss.messaging:service=PostOffice{Create:Configured}
jboss.messaging:service=PostOffice
-> jboss.jgroups:service=ChannelFactory{Create:** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory **}
*** CONTEXTS IN ERROR: Name -> Error
jboss.jgroups:service=ChannelFactory -> ** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory **
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:676)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Plz. help me out
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178864#4178864
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178864
17 years, 7 months
[JBoss Portal] - Configure dashboard invalid regions after layout change
by esmith1
This is a Configure Dashboard problem that occurs when a layout is changed and the region names of the new layout are not the same as the previous layout: for instance going from generic (center, left) to modified3Column (left, middle, right).
What happens: the Page Layout area does a (partial?) refresh and APPEARS correctly, but if you examine the HTML source it is using the old layout's region names. The impact is that -- for mislabelled regions -- if you ADD a portlet instance it will get added to the wrong region. For example after switching from generic to modified3Column, the second region listed is labelled "Middle" (correct) but the underyling Input button is named "layoutForm:a_left", so when you press ADD the portlet gets added to the Left region (wrong).
To see this problem you need to either modify one of the pre-delivered layouts, for instance renaming the "center" region to "middle" in the 3columns layout, done by changing these 2 files and restarting:
jboss-portal.sar/portal-core.war/layouts/3columns/index.jsp
jboss-portal.sar/portal-core.war/WEB-INF/portal-layouts.xml
or create a new layout, for instance one with "alpha", "beta", "gamma" regions.
Workaround: IF the user changes the LAYOUT and then leaves the Configure Dashboard and then re-enters the Configure Dashboard, the screen is fully refreshed and the Page Layout area is correctly rendered.
In this example I went from generic (center, left) to modified3Column (left, middle, right), notice the first region is labelled correct (left region) but the element names are incorrect (layoutForm:a_center):
<table width="100%">
| <tbody>
| <tr>
| <td colspan="3" class="portlet-form-field-label">
| <hr />
| left Region
| </td>
|
| </tr>
| <tr>
| <td valign="top"><input id="layoutForm:a_center" name="layoutForm:a_center" type="submit" value="Add" onclick="document.getElementById('blah').value=document.getElementById('windowForm:windowName').value;if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
| </td>
| <td width="100%"><select name="layoutForm:_id37jbpnsabcsnpbj" multiple="multiple" size="7" class="windowList portlet-form-field"> <option value="JSPPortletWindow">JSPPortletWindow</option> <option value="IdentityUserPortletWindow">IdentityUserPortletWindow</option></select>
| </td>
| <td valign="top" width="250"><input id="layoutForm:u_center" name="layoutForm:u_center" type="submit" value="Up" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" /><br /><input id="layoutForm:d_center" name="layoutForm:d_center" type="submit" value="Down" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
|
| <hr /><input id="layoutForm:l_center" name="layoutForm:l_center" type="submit" value="Delete" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
| </td>
| </tr>
| <tr>
| <td colspan="3" class="portlet-form-field-label">
| <hr />
| middle Region
| </td>
| </tr>
|
| <tr>
| <td valign="top"><input id="layoutForm:a_left" name="layoutForm:a_left" type="submit" value="Add" onclick="document.getElementById('blah').value=document.getElementById('windowForm:windowName').value;if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
| </td>
| <td width="100%"><select name="layoutForm:_id45jbpnsabcsnpbj" multiple="multiple" size="7" class="windowList portlet-form-field"></select>
| </td>
| <td valign="top" width="250"><input id="layoutForm:u_left" name="layoutForm:u_left" type="submit" value="Up" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" /><br /><input id="layoutForm:d_left" name="layoutForm:d_left" type="submit" value="Down" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
| <hr /><input id="layoutForm:l_left" name="layoutForm:l_left" type="submit" value="Delete" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
| </td>
| </tr>
|
| <tr>
| <td colspan="3" class="portlet-form-field-label">
| <hr />
| right Region
| </td>
| </tr>
| <tr>
| <td valign="top"><input id="layoutForm:a_right" name="layoutForm:a_right" type="submit" value="Add" onclick="document.getElementById('blah').value=document.getElementById('windowForm:windowName').value;if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
| </td>
|
| <td width="100%"><select name="layoutForm:_id91jbpnsabcsnpbj" multiple="multiple" size="7" class="windowList portlet-form-field"></select>
| </td>
| <td valign="top" width="250"><input id="layoutForm:u_right" name="layoutForm:u_right" type="submit" value="Up" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" /><br /><input id="layoutForm:d_right" name="layoutForm:d_right" type="submit" value="Down" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
| <hr /><input id="layoutForm:l_right" name="layoutForm:l_right" type="submit" value="Delete" onclick="if(typeof window.clearFormHiddenParams_layoutForm!='undefined'){clearFormHiddenParams_layoutForm('layoutForm');}" class="portlet-form-button layout-button" />
| </td>
| </tr>
| </tbody>
| </table>
|
I have more examples if needed.
It seems like org.jboss.portal.core.admin.ui.dashboard.DashboardBean updateTheme() needs to force a full screen refresh somehow.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178861#4178861
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178861
17 years, 7 months