March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCOMMON-13) Release JBossCommon 1.0.4.GA

by Dimitris Andreadis (JIRA)

Release JBossCommon 1.0.4.GA ---------------------------- Key: JBCOMMON-13 URL: http://jira.jboss.com/jira/browse/JBCOMMON-13 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.4.GA -- 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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4255) Upgrade to jboss common 1.0.5.GA

by Dimitris Andreadis (JIRA)

Upgrade to jboss common 1.0.5.GA -------------------------------- Key: JBAS-4255 URL: http://jira.jboss.com/jira/browse/JBAS-4255 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.0.CR1 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.GA Need to update jboss common to incorprorate a couple of fixes. -- 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

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1330) Login page (and error) with I18N

by Antoine Herzog (JIRA)

Login page (and error) with I18N -------------------------------- Key: JBPORTAL-1330 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1330 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4.1 SP1 Environment: JBP 2.4.1 SP1 Reporter: Antoine Herzog Assigned To: Julien Viet Priority: Minor Would be good to have the login page with internationalization. in file attachement : the login.jsp and error.jsp, to put in the portal-server.war the resource bundle for english, french and spanish. and the css file for presentation (separate from the portal-style.css). the current Locale is supposed to be set in a cookie. (todo if not yet in your portal. See LocaleInterceptor and in forum). the code also have the session stored locale (but with comments). cookie is better : keep the user chosen locale, from one session to the other the look and feel of the page is the one coming from my portal the background image is not in the files. put your in place of. did not change things on the css... to do when integrating in JBP... or if you pick this up before then. css : put it with the layout other css ? and change the path in the jsp files... must add the jstl.jar and standard.jar in the WEB-INF/lib folder (provided in files, for more convenient). when error : the username is shown again as default. the cursor is in the password field, for direct retry. -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-934) Problem with paths containing space characters when executing EJB3StandaloneBootstrap.scanClasspath()

by Jean-Philippe Courson (JIRA)

Problem with paths containing space characters when executing EJB3StandaloneBootstrap.scanClasspath() ------------------------------------------------------------------------------------------------------ Key: EJBTHREE-934 URL: http://jira.jboss.com/jira/browse/EJBTHREE-934 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: Windows XP. JDK5 Reporter: Jean-Philippe Courson When starting JBoss embedded, EJB3StandaloneBootstrap.scanClasspath() has troubles with JARs in the classpath whose path contains space characters. The paths passed to the URI constructors should be URL encoded. java.lang.RuntimeException: java.lang.RuntimeException: Not a valid URL: file:/c:/Program Files/ant/lib/ant-launcher.jar at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:279) at com.cognitran.ata.ejb.accessory.attribute.DropdownsController2Test.startupEmbeddedJboss(DropdownsController2Test.java:63) at com.cognitran.ata.ejb.accessory.attribute.DropdownsController2Test.setUp(DropdownsController2Test.java:45) Caused by: java.lang.RuntimeException: Not a valid URL: file:/c:/Program Files/ant/lib/ant-launcher.jar at org.jboss.util.file.ArchiveBrowser.getBrowser(Unknown Source) at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:370) at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350) at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305) at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.create(EJB3StandaloneDeployer.java:440) at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:273) ... 26 more Caused by: java.net.URISyntaxException: Illegal character in path at index 16: file:/c:/Program Files/ant/lib/ant-launcher.jar at java.net.URI$Parser.fail(URI.java:2816) at java.net.URI$Parser.checkChars(URI.java:2989) at java.net.URI$Parser.parseHierarchical(URI.java:3073) at java.net.URI$Parser.parse(URI.java:3021) at java.net.URI.<init>(URI.java:578) ... 32 more -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCOMMON-21) Add entries in JBossEntityResolver for service-ref_4_0.dtd/service-ref_4_2.dtd

by Dimitris Andreadis (JIRA)

Add entries in JBossEntityResolver for service-ref_4_0.dtd/service-ref_4_2.dtd ------------------------------------------------------------------------------ Key: JBCOMMON-21 URL: http://jira.jboss.com/jira/browse/JBCOMMON-21 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-old, core Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.5.GA, 2.0.4.GA registerEntity("-//JBoss//DTD Web Service Reference 4.0//EN", "service-ref_4_0.dtd"); registerEntity("-//JBoss//DTD Web Service Reference 4.2//EN", "service-ref_4_2.dtd"); -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-2) process monitoring and statistics capabilities (BAM)

by Arjan van Bentem (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-2?page=comments#action_12357895 ] Arjan van Bentem commented on JBPM-2: ------------------------------------- > ... using LoggingSession#findLogsByProcessInstance. Given these details one > can manually recreate the task instance objects, et cetera, to display information. Sorry for messing up this feature request... I just found that the derived classes of ProcessLog already provide methods such as TaskLog#getTaskInstance. So, no need for any manual work here! In fact, the web console shows some of these details on Process Instance View, History. So I guess that the full-blown history can easily be created using LoggingSession#findLogsByProcessInstance, and does not need to be taken into account if ever implementing this feature request. I still like the idea of this feature request though! For API see http://docs.jboss.com/jbpm/v3/javadoc/org/jbpm/logging/log/ProcessLog.html Arjan. > process monitoring and statistics capabilities (BAM) > ---------------------------------------------------- > > Key: JBPM-2 > URL: http://jira.jboss.com/jira/browse/JBPM-2 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Environment: N/A > Reporter: Ronald van Kuijk > Priority: Blocker > > JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=4990... > 1. jBPM should store the duration and start date of a state/process in the logs > 2. Write some detailed info on wiki > 3. Show processinstance and data > 4. day/week/month overviews > 5. near realtime data per process > 6. produce graphs of day/week/month overviews > Some more ideas i got from a requirements document... > - Number of cases processed in through a particular process definition > - Number of cases flowing through a particular activity > - Longest work item delay by activity > - Workitems awaiting a particular task > - Workitems in a specific worklist claimed and/or completed by a particular user > - Longest end-to-end delay > - Mean time to approve by activity by participant > - Mean end-to-end completion time. > as background info, here's what the competition says about BAM: > http://appian.com/AppianEnt/Analytics/analytics.html > http://www.webmethods.com/meta/default/folder/0000005936 > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduc... > http://www.tibco.com/software/business_optimization/activity_monitoring.j... > http://www.vitria.com/products/platform/bam.html > http://looselycoupled.com/glossary/BAM -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-2) process monitoring and statistics capabilities (BAM)

by Arjan van Bentem (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-2?page=comments#action_12357894 ] Arjan van Bentem commented on JBPM-2: ------------------------------------- And *maybe* related if it comes to an implementation: I'd like a way to get the full-blown history of a process instance, for example to get all task instances that have been completed so far. For me, this would also need to support sub-processes, loops and maybe even tokens that somehow have been moved to a specific point by an administrator... I think that GraphElement#getParents() cannot be used to get the full task history, as (as far as I can tell) that would not know about loops, nor would support sub-processes that have been assigned at runtime (like when a process-state has no sub-process defined in its XML definition, and is somehow selected and set at runtime). Currently the logs can (probably) be used to build such chain, like by using LoggingSession#findLogsByProcessInstance. Given these details one can manually recreate the task instance objects, et cetera, to display information. If I ever get to that I'll share it... Arjan. > process monitoring and statistics capabilities (BAM) > ---------------------------------------------------- > > Key: JBPM-2 > URL: http://jira.jboss.com/jira/browse/JBPM-2 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Environment: N/A > Reporter: Ronald van Kuijk > Priority: Blocker > > JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=4990... > 1. jBPM should store the duration and start date of a state/process in the logs > 2. Write some detailed info on wiki > 3. Show processinstance and data > 4. day/week/month overviews > 5. near realtime data per process > 6. produce graphs of day/week/month overviews > Some more ideas i got from a requirements document... > - Number of cases processed in through a particular process definition > - Number of cases flowing through a particular activity > - Longest work item delay by activity > - Workitems awaiting a particular task > - Workitems in a specific worklist claimed and/or completed by a particular user > - Longest end-to-end delay > - Mean time to approve by activity by participant > - Mean end-to-end completion time. > as background info, here's what the competition says about BAM: > http://appian.com/AppianEnt/Analytics/analytics.html > http://www.webmethods.com/meta/default/folder/0000005936 > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduc... > http://www.tibco.com/software/business_optimization/activity_monitoring.j... > http://www.vitria.com/products/platform/bam.html > http://looselycoupled.com/glossary/BAM -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4167) JMX Console not secured by default

by Ryan Campbell (JIRA)

JMX Console not secured by default ---------------------------------- Key: JBAS-4167 URL: http://jira.jboss.com/jira/browse/JBAS-4167 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ryan Campbell Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 The jmx and web consoles should be inaccessible to remote hosts by default upon installation. However, I just installed the alpha build and was able to access the jmx console remotely. Steps to reproduce ./run.sh -b $MYTESTIP Everything starts up correctly. However, I can access $MYTESTIP:8080/jmx-console from my browser without restriction -- 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

19 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-4106) Allow use of classes from scoped loaders in ClusterPartition RPC calls

by Brian Stansberry (JIRA)

Allow use of classes from scoped loaders in ClusterPartition RPC calls ---------------------------------------------------------------------- Key: JBAS-4106 URL: http://jira.jboss.com/jira/browse/JBAS-4106 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta2 ClusterPartition RPC calls will currently fail if any classes in the RPC or in the return value are not visible to ClusterPartition's classloader. This is because message unmarshalling will fail to resolve the scoped class. To fix this: 1) Add overloaded method registerRPCHandler(String key, Object handler, Classloader classloader) to ClusterPartition. 2) Add field ConcurrentHashMap<String, WeakReference<Classloader>> to ClusterPartition. 3) Refactor the way the service name is passed in the marshalled RPC. Now it is dot appended to the RPC's method name. Instead marshall it separately; e.g. the marshalled data structure could be new Object[] { serviceName, new MarshalledValue(methodCall) } or something like that. 4) Unmarshalling deserializes the above, reads the serviceName, looks up the classloader in the map; if found sets the TCCL, and then calls MarshalledValue.get() to get the MethodCall. Alternative is not to create a separate map for the classloaders, but change the current map that stores the handlers to instead store a simple data type that wraps the handler and the classloader. Have to use a WeakReference for the classloader though. The existing usage where no classloader is registered still has to work; i.e. if no classloader is found don't touch the TCCL. -- 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

19 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-725) Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files.

by Stefan Lang (JIRA)

Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files. -------------------------------------------------------------------------------------- Key: JBPM-725 URL: http://jira.jboss.com/jira/browse/JBPM-725 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM 3.1.2, jBPM 3.1.1 Reporter: Stefan Lang Assigned To: Tom Baeyens The auto-import attribute of the hibernate-mapping elements in all hbm.xml files is not set. Thus it is possible to use unqualified class names in Hibernate queries. The problem is that name clashes with client code are very probable. E.g. we have an "Event" entity class, jbpm has one too, so the following: "select Event as e ..." causes a hibernate exception. We have set the auto-import attribute to "false" in all jbpm hbm files and it works now as expected. -- 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

19 years, 3 months

3
3
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 March 2007