January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1857) RSS portlets (News, Weather) must allow proxy and HTTP authentication settings to be configured at runtime

by dpocock (JIRA)

RSS portlets (News, Weather) must allow proxy and HTTP authentication settings to be configured at runtime ---------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1857 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1857 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.6.3 Final Environment: Debian, JBoss 4.2.1.GA Reporter: dpocock The following parameters need to be configurable for the news and weather portlets: - HTTP username for the RSS server - HTTP password for the RSS server - HTTP proxy hostname - HTTP proxy port number - HTTP proxy username - HTTP proxy password It should be possible to define these settings differently for every portlet instance in the portal. A workaround exists for using a proxy, but it causes the same proxy settings to be used for all portlets. The workaround: add the following to the JAVA_OPTS in $JBOSS_HOME/bin/run.conf: -Dhttp.proxyHost=192.168.1.1 -Dhttp.proxyPort=3128 -Dhttp.nonProxyHosts=192.168.1|localhost There are more proxy options (HTTPS, FTP, etc) describe here: http://java.sun.com/j2se/1.5.0/docs/guide/net/proxies.html -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1237) Version info not available with java -jar

by Manik Surtani (JIRA)

Version info not available with java -jar ------------------------------------------ Key: JBCACHE-1237 URL: http://jira.jboss.com/jira/browse/JBCACHE-1237 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Probably something to do with the way maven builds the jar. -- 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

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1244) Buddy Manager to create _BUDDY_BACKUP_ region on initialisation before accepting any state or membership requests from buddies

by Manik Surtani (JIRA)

Buddy Manager to create _BUDDY_BACKUP_ region on initialisation before accepting any state or membership requests from buddies ------------------------------------------------------------------------------------------------------------------------------ Key: JBCACHE-1244 URL: http://jira.jboss.com/jira/browse/JBCACHE-1244 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Buddy Replication Affects Versions: 2.1.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Prevents a race condition in creating the node on the fly, causing potential timeout exceptions. -- 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

18 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1249) Replication exceptions should not propagate to cache caller

by Manik Surtani (JIRA)

Replication exceptions should not propagate to cache caller ----------------------------------------------------------- Key: JBCACHE-1249 URL: http://jira.jboss.com/jira/browse/JBCACHE-1249 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.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

18 years, 4 months

1
2
0 / 0

[JBoss JIRA] Updated: (GPD-179) pages.xml doesn't work with pageflow editor

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/GPD-179?page=all ] Koen Aers updated GPD-179: -------------------------- Fix Version/s: jBPM jPDL Designer 3.1.3 (was: jBPM jPDL Designer 3.1.2) > pages.xml doesn't work with pageflow editor > ------------------------------------------- > > Key: GPD-179 > URL: http://jira.jboss.com/jira/browse/GPD-179 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Reporter: Max Andersen > Assigned To: Koen Aers > Fix For: jBPM jPDL Designer 3.1.3 > > > a pages.xml with a proper page flow syntax does not have the pageflow editor in the right click menu. > and when using Open with... and choosing jBpm pageflow designer (not the correct name is it ?) I get > java.lang.NullPointerException > at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addProcessDiagramDimension(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.initInput(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.init(Unknown Source) > at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186) > at org.jbpm.ui.pageflow.editor.PageFlowEditor.addGraphPage(Unknown Source) > at org.jbpm.ui.pageflow.editor.PageFlowEditor.createPages(Unknown Source) > at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283) > at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) > at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426) > at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592) > at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633) -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-138) error dialogue appears on task panel of properties for task node

by Ross McDonald (JIRA)

error dialogue appears on task panel of properties for task node ---------------------------------------------------------------- Key: GPD-138 URL: http://jira.jboss.com/jira/browse/GPD-138 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.beta1 Environment: os x macbok pro, eclipse 3.3.0 Reporter: Ross McDonald Assigned To: Koen Aers Priority: Minor Hi, when working with the designer in eclipse, if I put a new task node on the screen, immediately enter a value against the name on the 'general' panel under properties, then click on the tasks panel under properties, I get an error dialogue with the following details : Reason: 0 'An error has occurred. See error log for more details. 0 On the other hand, if after entering a name, I click on the description input field, but do not enter anything, then click on the task panel under properties, there is no error. -- 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

18 years, 4 months

2
16
0 / 0

[JBoss JIRA] Created: (GPD-168) feature not recognized

by Joachim Neubert (JIRA)

feature not recognized ---------------------- Key: GPD-168 URL: http://jira.jboss.com/jira/browse/GPD-168 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM JPDL Designer 3.1.0.GA Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1 Reporter: Joachim Neubert Assigned To: Koen Aers After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse. -- 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

18 years, 4 months

3
7
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-472) problem with mail

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-472?page=all ] Carlo de Wolf updated EJBTHREE-472: ----------------------------------- Fix Version/s: HEAD (was: AS 5.0.0.Beta3) > problem with mail > ----------------- > > Key: EJBTHREE-472 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-472 > Project: EJB 3.0 > Issue Type: Bug > Reporter: Bill Burke > Assigned To: William DeCoste > Fix For: HEAD > > -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-405) Allow EJB Container's ObjectName to be configurable through annotation or XML

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-405?page=all ] Carlo de Wolf updated EJBTHREE-405: ----------------------------------- Fix Version/s: HEAD (was: AS 5.0.0.Beta3) > Allow EJB Container's ObjectName to be configurable through annotation or XML > ----------------------------------------------------------------------------- > > Key: EJBTHREE-405 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-405 > Project: EJB 3.0 > Issue Type: Feature Request > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: HEAD > > -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-575) Access configuration attributes through JMX

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-575?page=all ] Carlo de Wolf updated EJBTHREE-575: ----------------------------------- Fix Version/s: HEAD (was: AS 5.0.0.Beta3) > Access configuration attributes through JMX > ------------------------------------------- > > Key: EJBTHREE-575 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-575 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: EJB 3.0 RC7 - FD > Reporter: Darran Lofthouse > Fix For: HEAD > > > This might be more appropriate split into a number of tasks but for the moment I am raising it as a single issue. > There are a number of properties that can be set on message driven beans using activation config properties e.g. 'maxPoolSize'. After deployment there is not a mechanism to check that the correct properties have been applied. It would be good to be able to inspect the configuration values using JMX. > Using the @PoolClass annotation it is possible to configure the pool that is used for the EJB, it would also be good if this configuration information could also be made available using JMX. > For the configuration items it would also be good if the attributes could be updated using JMX. > Finally providing status information such as current pool sizes through JMX would also help users check the configuration they have selected is appropriate. -- 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

18 years, 4 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-jira January 2008