July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBFORUMS-95) Authorization support of conditional usecases

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBFORUMS-95?page=all ] Sohil Shah resolved JBFORUMS-95. -------------------------------- Resolution: Done > Authorization support of conditional usecases > --------------------------------------------- > > Key: JBFORUMS-95 > URL: http://jira.jboss.com/jira/browse/JBFORUMS-95 > Project: JBoss Forums > Issue Type: Feature Request > Components: Java Server Faces based UIController layer > Reporter: Ryszard Kozmik > Assigned To: Sohil Shah > Fix For: 1.0.0 Alpha > > > I would like to have kind of "else" in "isAllowed" tag which would give me possibility to show user some text that he is not allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBFORUMS-95) Authorization support of conditional usecases

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBFORUMS-95?page=comments#action_12339535 ] Sohil Shah commented on JBFORUMS-95: ------------------------------------ And.. <isAllowedChoose> <isAllowedWhen fragment="fragmentId" contextData="comma-separated list of data for criteria checking">  </isAllowedWhen> <isAllowedOtherwise>  </isAllowedOtherwise> </isAllowedChoose> > Authorization support of conditional usecases > --------------------------------------------- > > Key: JBFORUMS-95 > URL: http://jira.jboss.com/jira/browse/JBFORUMS-95 > Project: JBoss Forums > Issue Type: Feature Request > Components: Java Server Faces based UIController layer > Reporter: Ryszard Kozmik > Assigned To: Sohil Shah > Fix For: 1.0.0 Alpha > > > I would like to have kind of "else" in "isAllowed" tag which would give me possibility to show user some text that he is not allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBFORUMS-95) Authorization support of conditional usecases

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBFORUMS-95?page=comments#action_12339534 ] Sohil Shah commented on JBFORUMS-95: ------------------------------------ So now there are two types of tags that can be used in the UI facelet layer to apply fine grained security: <isAllowed fragment="fragmentId" contextData="comma-separated list of data for criteria checking"> </isAllowed> > Authorization support of conditional usecases > --------------------------------------------- > > Key: JBFORUMS-95 > URL: http://jira.jboss.com/jira/browse/JBFORUMS-95 > Project: JBoss Forums > Issue Type: Feature Request > Components: Java Server Faces based UIController layer > Reporter: Ryszard Kozmik > Assigned To: Sohil Shah > Fix For: 1.0.0 Alpha > > > I would like to have kind of "else" in "isAllowed" tag which would give me possibility to show user some text that he is not allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-339) JBoss v2.0.0 Alpha -> Installed but invisible on Eclipse v3.2

by Graham Leggett (JIRA)

JBoss v2.0.0 Alpha -> Installed but invisible on Eclipse v3.2 ------------------------------------------------------------- Key: JBIDE-339 URL: http://jira.jboss.com/jira/browse/JBIDE-339 Project: JBoss IDE Issue Type: Bug Components: JBossIDE Core Affects Versions: 2.0.0.Alpha Reporter: Graham Leggett Assigned To: Marshall Culpepper Priority: Critical After giving up on the v1.6.0 JBoss Eclipse plugin in Eclipse v3.2, I moved the update site from the stable URL to the development URL, and Eclipse update installed JBoss IDE v2.0.0 Alpha. Running the "debug" option in Eclipse, all of the JBoss run options, which were broken in v1.6.0, are now entirely missing. The only option present is "JBoss AOP Application". This means v2.0.0 Alpha is also dead in the water under Eclipse v3.2. Eclipse v3.2 has been out for over a month, and milestone releases long before that, and there is no clear indication which version of the JBoss IDE is supposed to work correctly. Is the JBoss plugin still being maintained? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

3
2
0 / 0

[JBoss JIRA] Closed: (JBAS-3281) javax.management.timer.Timer should perform fixed-delay periodic execution by default

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3281?page=all ] Dimitris Andreadis closed JBAS-3281. ------------------------------------ Resolution: Done > javax.management.timer.Timer should perform fixed-delay periodic execution by default > ------------------------------------------------------------------------------------- > > Key: JBAS-3281 > URL: http://jira.jboss.com/jira/browse/JBAS-3281 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA > Environment: Java 1.4 (For Java 5.0 we use the implementation supplied with the JRE) > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > The implementation of javax.management.timer.Timer does not match the javadoc: - > http://java.sun.com/j2ee/1.4/docs/api/javax/management/timer/Timer.html > By default the timer should be using fixed-delay execution, our implementation is defaulting to fixed-rate execution. > In addition to this to use fixed-rate execution you should use the method addNotification(String, String, Object, Date, long, long, boolean), however we have not implemented this method and we just throw a RuntimeException if it is invoked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3281) javax.management.timer.Timer should perform fixed-delay periodic execution by default

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3281?page=all ] Dimitris Andreadis updated JBAS-3281: ------------------------------------- Fix Version/s: (was: JBossAS-3.2.8.SP2) Affects Version/s: (was: JBossAS-3.2.8.SP1) > javax.management.timer.Timer should perform fixed-delay periodic execution by default > ------------------------------------------------------------------------------------- > > Key: JBAS-3281 > URL: http://jira.jboss.com/jira/browse/JBAS-3281 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA > Environment: Java 1.4 (For Java 5.0 we use the implementation supplied with the JRE) > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta > > > The implementation of javax.management.timer.Timer does not match the javadoc: - > http://java.sun.com/j2ee/1.4/docs/api/javax/management/timer/Timer.html > By default the timer should be using fixed-delay execution, our implementation is defaulting to fixed-rate execution. > In addition to this to use fixed-rate execution you should use the method addNotification(String, String, Object, Date, long, long, boolean), however we have not implemented this method and we just throw a RuntimeException if it is invoked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-3281) javax.management.timer.Timer should perform fixed-delay periodic execution by default

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3281?page=all ] Dimitris Andreadis reopened JBAS-3281: -------------------------------------- > javax.management.timer.Timer should perform fixed-delay periodic execution by default > ------------------------------------------------------------------------------------- > > Key: JBAS-3281 > URL: http://jira.jboss.com/jira/browse/JBAS-3281 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 > Environment: Java 1.4 (For Java 5.0 we use the implementation supplied with the JRE) > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2 > > > The implementation of javax.management.timer.Timer does not match the javadoc: - > http://java.sun.com/j2ee/1.4/docs/api/javax/management/timer/Timer.html > By default the timer should be using fixed-delay execution, our implementation is defaulting to fixed-rate execution. > In addition to this to use fixed-rate execution you should use the method addNotification(String, String, Object, Date, long, long, boolean), however we have not implemented this method and we just throw a RuntimeException if it is invoked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3389) JBossAS 3.2.8SP1 triggers JVM 1.4.2 internal error with -Xrunhprof and -XX:+UseParallelGC enabled

by Francisco Pereira (JIRA)

JBossAS 3.2.8SP1 triggers JVM 1.4.2 internal error with -Xrunhprof and -XX:+UseParallelGC enabled ------------------------------------------------------------------------------------------------- Key: JBAS-3389 URL: http://jira.jboss.com/jira/browse/JBAS-3389 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-3.2.8.SP1 Environment: OS: SuSE Linux 10.0 - kernel 2.6.13-15.10-default. JAVA: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06) Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode) HW: x86 - the Linux server is running as a guest OS in a MS Virtual Server 2005 R2 host Reporter: Francisco Pereira When starting JBoss 3.2.8SP1, JVM crashes if both -Xrunhprof and -XX:+UseParallelGC options are enabled. JVM crash was reported to Sun, and they said that the crash is triggered by JBossAS and I should ask JBoss to investigate this issue. Following is the JVM crash logfile. # # An unexpected error has been detected by HotSpot Virtual Machine: # # Internal Error (504152414C4C454C33434156454E4745284541500E435050022F), pid=18608, tid=1658059696 # # Java VM: Java HotSpot(TM) Server VM (1.4.2_11-b06 mixed mode) --------------- T H R E A D --------------- Current thread (0x080ca010): JavaThread "Reference Handler" daemon [_thread_in_vm, id=18608] Stack: [0x62ccd000,0x62d40000), sp=0x62d3e96c, free space=454k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [libjvm.so+0x4599ad] V [libjvm.so+0x24f2aa] V [libjvm.so+0x3c4be4] V [libjvm.so+0x448b23] V [libjvm.so+0x24cc99] V [libjvm.so+0x3b2aff] V [libjvm.so+0x21964b] V [libjvm.so+0x21b8dd] V [libjvm.so+0x21f17d] V [libjvm.so+0x41aae7] V [libjvm.so+0x41a5fc] V [libjvm.so+0x41e622] V [libjvm.so+0x419824] V [libjvm.so+0x24d640] V [libjvm.so+0x2c66d0] j java.lang.ref.Reference$ReferenceHandler.run()V+71 v ~StubRoutines::call_stub V [libjvm.so+0x2d10b4] V [libjvm.so+0x3b8945] V [libjvm.so+0x2d1306] V [libjvm.so+0x2d0bd6] V [libjvm.so+0x2d174f] V [libjvm.so+0x32b525] V [libjvm.so+0x4361da] V [libjvm.so+0x4313f3] V [libjvm.so+0x3ba473] C [libpthread.so.0+0x5297] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j java.lang.ref.Reference$ReferenceHandler.run()V+71 v ~StubRoutines::call_stub --------------- P R O C E S S --------------- Java Threads: ( => current thread ) 0x080ca800 JavaThread "Finalizer" daemon [_thread_blocked, id=18608] =>0x080ca010 JavaThread "Reference Handler" daemon [_thread_in_vm, id=18608] 0x080581a0 JavaThread "main" [_thread_in_vm, id=18608] Other Threads: 0x080c9530 VMThread [id=18608] VM state:not at safepoint (normal execution) VM Mutex/Monitor currently owned by a thread: None Heap PSYoungGen total 3968K, used 0K [0x45a00000, 0x45e00000, 0x48670000) eden [0x45a00000,0x45a00000,0x45dc0000) from [0x45de0000,0x45de0000,0x45e00000) to [0x45dc0000,0x45dc0000,0x45de0000) PSOldGen total 6528K, used 80K [0x48670000, 0x48cd0000, 0x5ea00000) object [0x48670000,0x486842b8,0x48cd0000) PSPermGen total 16384K, used 863K [0x5ea00000, 0x5fa00000, 0x62a00000) object [0x5ea00000,0x5ead7e58,0x5fa00000) Dynamic libraries: 08048000-08053000 r-xp 00000000 03:01 36947 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/bin/java 08053000-08055000 rwxp 0000a000 03:01 36947 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/bin/java 08055000-080ff000 rwxp 08055000 00:00 0 [heap] 40000000-40015000 r-xp 00000000 03:01 3279 /lib/ld-2.3.5.so 40015000-40017000 rwxp 00014000 03:01 3279 /lib/ld-2.3.5.so 40017000-4001b000 rwxs 00000000 03:01 53907 /tmp/hsperfdata_jboss/18608 4001b000-4001c000 rwxp 4001b000 00:00 0 4001d000-4001e000 rwxp 4001d000 00:00 0 4001e000-4002c000 r-xp 00000000 03:01 3329 /lib/tls/libpthread-2.3.5.so 4002c000-4002e000 rwxp 0000d000 03:01 3329 /lib/tls/libpthread-2.3.5.so 4002e000-40030000 rwxp 4002e000 00:00 0 40030000-40032000 r-xp 00000000 03:01 3294 /lib/libdl-2.3.5.so 40032000-40034000 rwxp 00001000 03:01 3294 /lib/libdl-2.3.5.so 40034000-4014d000 r-xp 00000000 03:01 3325 /lib/tls/libc-2.3.5.so 4014d000-4014e000 r-xp 00119000 03:01 3325 /lib/tls/libc-2.3.5.so 4014e000-40151000 rwxp 0011a000 03:01 3325 /lib/tls/libc-2.3.5.so 40151000-40154000 rwxp 40151000 00:00 0 40154000-4071d000 r-xp 00000000 03:01 38121 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/server/libjvm.so 4071d000-40777000 rwxp 005c8000 03:01 38121 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/server/libjvm.so 40777000-4078c000 rwxp 40777000 00:00 0 4078c000-4079e000 r-xp 00000000 03:01 3299 /lib/libnsl-2.3.5.so 4079e000-407a0000 rwxp 00011000 03:01 3299 /lib/libnsl-2.3.5.so 407a0000-407a2000 rwxp 407a0000 00:00 0 407a2000-407c6000 r-xp 00000000 03:01 3327 /lib/tls/libm-2.3.5.so 407c6000-407c8000 rwxp 00023000 03:01 3327 /lib/tls/libm-2.3.5.so 407c8000-407ce000 r-xp 00000000 03:01 38117 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/native_threads/libhpi.so 407ce000-407d0000 rwxp 00005000 03:01 38117 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/native_threads/libhpi.so 407d0000-40805000 r-xs 00000000 03:01 49081 /var/run/nscd/passwd 40805000-40812000 r-xp 00000000 03:01 38114 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/libverify.so 40812000-40814000 rwxp 0000c000 03:01 38114 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/libverify.so 40814000-40830000 r-xp 00000000 03:01 38102 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/libjava.so 40830000-40832000 rwxp 0001b000 03:01 38102 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/libjava.so 40832000-40840000 r-xp 00000000 03:01 38115 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/libzip.so 40840000-40842000 rwxp 0000d000 03:01 38115 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/libzip.so 40842000-421ec000 r-xs 00000000 03:01 38167 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/rt.jar 421ec000-42236000 rwxp 421ec000 00:00 0 42236000-4224c000 r-xs 00000000 03:01 38172 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/sunrsasign.jar 4224c000-42329000 r-xs 00000000 03:01 38136 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/jsse.jar 42329000-4233b000 r-xs 00000000 03:01 38135 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/jce.jar 4233b000-42910000 r-xs 00000000 03:01 38018 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/charsets.jar 42910000-42b50000 rwxp 42910000 00:00 0 42b50000-45910000 rwxp 42b50000 00:00 0 45910000-45919000 rwxp 45910000 00:00 0 45919000-459d0000 rwxp 45919000 00:00 0 459d0000-459f8000 rwxp 459d0000 00:00 0 45a00000-45e00000 rwxp 45a00000 00:00 0 45e00000-48670000 rwxp 45e00000 00:00 0 48670000-48cd0000 rwxp 48670000 00:00 0 48cd0000-5ea00000 rwxp 48cd0000 00:00 0 5ea00000-5fa00000 rwxp 5ea00000 00:00 0 5fa00000-62a00000 rwxp 5fa00000 00:00 0 62a00000-62a02000 rwxp 62a00000 00:00 0 62a02000-62a16000 rwxp 62a02000 00:00 0 62a16000-62a1a000 rwxp 62a16000 00:00 0 62a1a000-62ac8000 rwxp 62a1a000 00:00 0 62ac8000-62ad0000 rwxp 62ac8000 00:00 0 62ad0000-62ae8000 rwxp 62ad0000 00:00 0 62ae8000-62bbd000 rwxp 62ae8000 00:00 0 62bbd000-62bbe000 ---p 62bbd000 00:00 0 62bbe000-62c3e000 rwxp 62bbe000 00:00 0 62c3e000-62c3f000 ---p 62c3e000 00:00 0 62c3f000-62cbf000 rwxp 62c3f000 00:00 0 62cbf000-62cc0000 ---p 62cbf000 00:00 0 62cc0000-62ccd000 rwxp 62cc0000 00:00 0 62ccd000-62cd0000 ---p 62ccd000 00:00 0 62cd0000-62d40000 rwxp 62cd0000 00:00 0 62d40000-62d41000 ---p 62d40000 00:00 0 62d41000-62d4e000 rwxp 62d41000 00:00 0 62d4e000-62d51000 ---p 62d4e000 00:00 0 62d51000-62dc1000 rwxp 62d51000 00:00 0 62dc1000-62dcf000 r-xp 00000000 03:01 38099 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/libhprof.so 62dcf000-62dd0000 rwxp 0000d000 03:01 38099 /usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/libhprof.so 62dd0000-62e11000 rwxp 62dd0000 00:00 0 bf67b000-bf685000 rwxp bf67b000 00:00 0 bf685000-bf688000 ---p bf685000 00:00 0 bf863000-bf878000 rwxp bf863000 00:00 0 [stack] ffffe000-fffff000 ---p 00000000 00:00 0 [vdso] VM Arguments: jvm_args: -Xmx400m -Djava.awt.headless=true -XX:+UseParallelGC -verbose:gc -Xloggc:/var/log/jboss/gc-20060711-155153.log -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xrunhprof:file=/var/log/jboss/hat-20060711-155153.hprof,format=b -DJAVA_ENV=local -Dsalmon.props.path=/usr/local/jboss/server/default/conf/properties Environment Variables: JAVA_HOME=/usr/lib/jvm/java JRE_HOME=/usr/lib/jvm/java/jre PATH=/opt/gnome/sbin:/root/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin LD_LIBRARY_PATH=/usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386/server:/usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/lib/i386:/usr/lib/jvm/java-1.4.2-sun-1.4.2.11/jre/../lib/i386 SHELL=/bin/bash HOSTTYPE=i386 OSTYPE=linux MACHTYPE=i686-suse-linux --------------- S Y S T E M --------------- OS:SUSE LINUX 10.0 (i586) OSS VERSION = 10.0 uname:Linux 2.6.13-15.10-default #1 Fri May 12 16:27:12 UTC 2006 i686 libc:glibc 2.3.5 NPTL 2.3.5 rlimit: STACK infinity, CORE 0k, NPROC 4095, NOFILE 1024, AS infinity load average:0.00 0.00 14276993196626418462795770804590052381274234326367887214290738774341058560.00 CPU:total 1 family 15, cmov, cx8, fxsr, mmx, sse, sse2 Memory: 4k page, physical 515780k(40476k free), swap 514040k(510900k free) vm_info: Java HotSpot(TM) Server VM (1.4.2_11-b06) for linux-x86, built on Feb 13 2006 10:30:04 by unknown with unknown compiler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

2
2
0 / 0

[JBoss JIRA] Commented: (JBAS-3376) PooledInvokerHA returning java.rmi.MarshalledObject

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3376?page=comments#action_12339528 ] Clebert Suconic commented on JBAS-3376: --------------------------------------- for the record, tag created using this command: cvs rtag -r JBoss_4_0_3_SP1 -b JBoss_4_0_4_SP1_JBAS-3376 jboss-4.0.x > PooledInvokerHA returning java.rmi.MarshalledObject > --------------------------------------------------- > > Key: JBAS-3376 > URL: http://jira.jboss.com/jira/browse/JBAS-3376 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Clebert Suconic > Assigned To: Clebert Suconic > > This is causing bottlenecks specially on JVM 1.5, as java.rmi.MarshalledOutputStream takes a long time annotating classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-303) Treat unnamed transition as default one

by Raul Piaggio (JIRA)

Treat unnamed transition as default one --------------------------------------- Key: JBSEAM-303 URL: http://jira.jboss.com/jira/browse/JBSEAM-303 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Raul Piaggio Priority: Minor In a pageflow, whenever there's no matching transition on a (start-state or decision) node, the flow will fail to land on a page node, resulting in a runtime exception (ClassCastException on org.jboss.seam.core.Pageflow.getPage()). Suggestion: if there's an unnamed transition (i.e: <transition to="menu"></transition>, without "name" property) trigger it when no other transition maches. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2006