April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBAS-8475) Add Mojarra 2.0.4 workaround information to the AS/JSK integration wiki

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/JBAS-8475?page=com.atlassian.jira.plugin.... ] Stan Silvert resolved JBAS-8475. -------------------------------- Resolution: Out of Date > Add Mojarra 2.0.4 workaround information to the AS/JSK integration wiki > ----------------------------------------------------------------------- > > Key: JBAS-8475 > URL: https://issues.jboss.org/browse/JBAS-8475 > Project: Application Server 3 4 5 and 6 > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Integration, JSF > Affects Versions: 6.0.0.M4 > Reporter: Jay Balunas > Assignee: Stan Silvert > > See JBAS-8375 for the details. > If users want to use JSF RI 2.0.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBAS-8099) Lazy-load JSF configurations in JSF Deployer

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/JBAS-8099?page=com.atlassian.jira.plugin.... ] Stan Silvert resolved JBAS-8099. -------------------------------- Resolution: Out of Date > Lazy-load JSF configurations in JSF Deployer > -------------------------------------------- > > Key: JBAS-8099 > URL: https://issues.jboss.org/browse/JBAS-8099 > Project: Application Server 3 4 5 and 6 > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 6.0.0.M4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Priority: Minor > Fix For: No Release > > > The JSF configurations/implementations are loaded at startup by the JSF Deployer. This could improve startup a tiny bit if each were loaded on demand. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6573) JSR-236 Java EE 7 concurrency support parent issue

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6573?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-6573: ---------------------------------- Please open a separate top-level feature request JIRA for that. Thanks. > JSR-236 Java EE 7 concurrency support parent issue > -------------------------------------------------- > > Key: AS7-6573 > URL: https://issues.jboss.org/browse/AS7-6573 > Project: Application Server 7 > Issue Type: Enhancement > Components: EE > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 8.0.0.Alpha1 > > > Parent task for JSR-236 subtasks. Please resolve AS7-6430 only when this issue is resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBAS-8751) javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/JBAS-8751?page=com.atlassian.jira.plugin.... ] Stan Silvert resolved JBAS-8751. -------------------------------- Resolution: Rejected Closing as per AS7-5310 > javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored > ----------------------------------------------------------------------- > > Key: JBAS-8751 > URL: https://issues.jboss.org/browse/JBAS-8751 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 6.0.0.CR1 > Reporter: Nicklas Karlsson > Assignee: Stan Silvert > Fix For: No Release > > > Given a model like > @javax.enterprise.inject.Model > public class Model > { > private String data; > public String getData() > { > return data; > } > public void setData(String data) > { > System.out.println("set data to " + data); > this.data = data; > } > } > and a view like > <h:form> > <h:inputText id="field" value="#{model.data}"/> > <h:commandButton value="!"/> > </h:form> > an empty value is submitted even with > <context-param> > <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> > <param-value>true</param-value> > </context-param> > Debugging the application shows that the emptyStringIsNull of the component is true. > even with a @FacesConverter(forClass=String.class) which is correctly run and doing a setSubmittedValue(null), the model still sees a "" instead of a null > Tested to work correctly on a GF 3.0.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6573) JSR-236 Java EE 7 concurrency support parent issue

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/AS7-6573?page=com.atlassian.jira.plugin.s... ] Philippe Marschall commented on AS7-6573: ----------------------------------------- It would be great if AS8 went farther than the spec and provided a {{java.util.concurrent.ForkJoinPool}} and a {{java.util.concurrent.ForkJoinPool.ForkJoinWorkerThreadFactory}}. These don't have to (and probably shouldn't) preserve the context (see also http://java.net/projects/concurrency-ee-spec/lists/jsr236-experts/archive...). The advantage of this instead of manually creating a {{ForkJoinPool}} would be that it can be configured, managed and monitored in the server (and that threads are traditionally managed by the server). I'm well aware that this is unspecified behaviour but so is Infinispan in AS7 and AS8 since JSR-107 again didn't make it. Should I open a separate subtask for this? > JSR-236 Java EE 7 concurrency support parent issue > -------------------------------------------------- > > Key: AS7-6573 > URL: https://issues.jboss.org/browse/AS7-6573 > Project: Application Server 7 > Issue Type: Enhancement > Components: EE > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 8.0.0.Alpha1 > > > Parent task for JSR-236 subtasks. Please resolve AS7-6430 only when this issue is resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-120) JBoss build of jsf api contains incorrect xml header

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/JBEE-120?page=com.atlassian.jira.plugin.s... ] Stan Silvert resolved JBEE-120. ------------------------------- Resolution: Out of Date Closing as out of date. We are dropping JSF 1.2 from AS8. Since this doesn't cause any operational problems it doesn't seem worth fixing. If you disagree, please let me know and we can reopen. > JBoss build of jsf api contains incorrect xml header > ---------------------------------------------------- > > Key: JBEE-120 > URL: https://issues.jboss.org/browse/JBEE-120 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: general > Reporter: Paul Gier > Assignee: Stan Silvert > Fix For: JavaEE 5 Spec APIs - Maint > > > The JBoss rebuild of the jsf api jar contains an incorrect xml header missing the namespace. > https://repository.jboss.org/nexus/content/groups/public/javax/faces/jsf-... > Current header: > {code:xml} > <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > {code} > Correct header: > {code:xml} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6790) Multi-JSF doesn't understand new modules structure

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/AS7-6790?page=com.atlassian.jira.plugin.s... ] Stan Silvert commented on AS7-6790: ----------------------------------- Long term fix will be to eliminate directory scanning when some feature like MODULES-151 is implemented. > Multi-JSF doesn't understand new modules structure > -------------------------------------------------- > > Key: AS7-6790 > URL: https://issues.jboss.org/browse/AS7-6790 > Project: Application Server 7 > Issue Type: Bug > Components: JSF > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stan Silvert > Assignee: Stan Silvert > > With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default. > The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script. > See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6819: ---------------------------------- Fix Version/s: (was: 7.1.3.Final (EAP)) > MBD @ResourceAdapter deployment issue with JCA inbound listener > --------------------------------------------------------------- > > Key: AS7-6819 > URL: https://issues.jboss.org/browse/AS7-6819 > Project: Application Server 7 > Issue Type: Clarification > Components: EJB, JCA > Affects Versions: 7.1.3.Final (EAP) > Environment: Windows with Jboss 7.1.3 EAP version. > Reporter: Sudip Bhowmik > Labels: jboss > Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml > > > The source set is attached here with. > ================================================= > 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t > ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame > terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5579) standalone.bat using 'or' keyword for --debug parameter

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-5579?page=com.atlassian.jira.plugin.s... ] James Perkins closed AS7-5579. ------------------------------ Resolution: Won't Fix The {{-d}} option was removed and only the {{--debug}} is used. > standalone.bat using 'or' keyword for --debug parameter > ------------------------------------------------------- > > Key: AS7-5579 > URL: https://issues.jboss.org/browse/AS7-5579 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Environment: Windows 7 SP1 > Reporter: Bertrand Donnet > Assignee: Tomaz Cerar > Priority: Minor > > When using a parameter like --server-file with standalone.bat, at line 18, keyword 'or' prevents the IF test from working correctly and always set DEBUG mode. this is not supported in .BAT > ) else if "%1" == "--debug" or "%1" == "-d" ( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6822) standalone.bat has an error for setting debug mode with --debug

by James Perkins (JIRA)

James Perkins created AS7-6822: ---------------------------------- Summary: standalone.bat has an error for setting debug mode with --debug Key: AS7-6822 URL: https://issues.jboss.org/browse/AS7-6822 Project: Application Server 7 Issue Type: Bug Components: Scripts Reporter: James Perkins Assignee: James Perkins Priority: Minor Fix For: 8.0.0.Alpha1 In the released EAP 6.1.0-alpha, standalone.bat has these lines: {code} rem Set debug settings if not already set if "%DEBUG_MODE%" == "true" ( echo "%JAVA_OPTS%" | findstr /I "\-agentlib:jdwp" > nul if errorlevel == 1 ( echo Debug already enabled in JAVA_OPTS, ignoring --debug argument ) else ( set "JAVA_OPTS=%JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=%DEBUG_PORT%,server=y,suspend=n" ) ) {code} The check on the error level is wrong. If "findstr" *can* find the agentlib setting, then errorlevel will be 0. So the correction is: {code} if errorlevel == 1 ( {code} should be: {code} if errorlevel == 0 ( {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013