[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, 10 months
[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, 10 months
[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, 10 months
[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, 10 months
[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, 10 months