jboss-jira August 2009

jboss-jira@lists.jboss.org

2 participants
1934 discussions

[JBoss JIRA] Created: (GPD-356) Designer creates duplicate handler nodes under decision nodes

by Alfie Kirkpatrick (JIRA)

Designer creates duplicate handler nodes under decision nodes ------------------------------------------------------------- Key: GPD-356 URL: https://jira.jboss.org/jira/browse/GPD-356 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM jPDL Designer 4.0.0.GA Reporter: Alfie Kirkpatrick Assignee: Koen Aers Priority: Minor When switching between text mode and graphical mode and saving the process definition a few times a large number of handler elements can build up under each decision node. This doesn't seem to affect the running of the process so is more an inconvenience than anything, but could cause confusion if the handler parameters are modified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2440) Incorrect values of escapeXml in actionURL result in confusing NullPointerException in JBoss Portlet Container

by Bernard de Terwangne (JIRA)

Incorrect values of escapeXml in actionURL result in confusing NullPointerException in JBoss Portlet Container -------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-2440 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2440 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: Portlet-2.0.1 Environment: Any Reporter: Bernard de Terwangne Priority: Minor JSR-286 states that escapeXml defaults to true. This value is almost never appropriate. If you forget to set it to false explicitly (very common mistake) you get a very confusing and little explicit NullPointerException. I suggest to throw a more explicit exception so that developpers don't loose a lot of time wondering why their apps don't work. I can provide the fix if requested. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7146) org.apache.catalina.core.StandardServer of the JBoss-web.deployer systematicaly returns NULL against getGlobalNamingContext() call.

by Hideo GOTO (JIRA)

org.apache.catalina.core.StandardServer of the JBoss-web.deployer systematicaly returns NULL against getGlobalNamingContext() call. ----------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-7146 URL: https://jira.jboss.org/jira/browse/JBAS-7146 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.2.3.GA, JBossAS-4.2.2.GA Environment: Linux Fedora8(x386), Fedora8(x86_64) + jdk1.6.0_12 ( JBoss 4.2.2.GA and 4.2.3.GA just as it is unziped). Reporter: Hideo GOTO Assignee: Scott M Stark I am testing migration of an application running on standard Tomcat5/6 to JBoss AS. The application uses <GlobalNamingResources><resouce>definition in the server.xml. While testing, I found out that the getGlobalNamingContext() systematicaly returns NULL, although it is documented in JBoss-web's Java DOC just same as in the Tomcat's one Is it an intended behavior due to JBoss's proper JNDI concern? If yes, any alternative? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7145) New logging framework breakes JBossWS

by Richard Opalka (JIRA)

New logging framework breakes JBossWS ------------------------------------- Key: JBAS-7145 URL: https://jira.jboss.org/jira/browse/JBAS-7145 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: David Lloyd Fix For: JBossAS-6.0.0.Alpha1 We're using thirdparty components (to be concrete e.g. Apache WS-Policy) that require commons-logging artifact that have been removed from AS trunk :( Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.ws.policy.util.Loader.<clinit>(Loader.java:32) at org.apache.ws.policy.util.PolicyFactory.getPolicyReader(PolicyFactory.java:56) at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.processPolicyExtensions(PolicyMetaDataBuilder.java:155) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:92) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:138) at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:63) at javax.xml.ws.Service.<init>(Service.java:79) at javax.xml.ws.Service.create(Service.java:96) at org.jboss.test.ws.jaxws.jbws1666.TestClient.testPortAccess(TestClient.java:38) at org.jboss.test.ws.jaxws.jbws1666.TestClient.main(TestClient.java:48) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
4
0 / 0

← Newer
1
...
191
192
193
194
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2009