December 2013 - wildfly-dev - Jboss List Archives

by Cheng Fang

WildFly batch implementation currently supports a global batch job repository, with the plan to support per-application job repository. James and I have been tossing around a few ideas, and would like to get input on some implementation approaches. Here are some options: 1, introduce wildfly-batch.xml. Applications can package in wildfly-batch.xml to override batch subsystem configurations for this app. This gives applications maximum flexibility to customize any batch-related configurations that can be reasonably modified by application, including batch job repository datasource, thead pool, etc. But the downside is there is one more wildfly-specific deployment descriptors to deal with. 2, define various batch profile that applications can choose from. The CLI path would be something like subsystem=batch/profile=A where A would be the name of the profile and would have the same settings as a root (subsystem=batch). If something, e.g. a thread-pool, isn't defined on the profile it falls back to the default. The user would define the profile by adding a MANIFEST.MF entry with something like Batch-Profile: A. This approach avoids the need for wildfly-batch.xml, but including application config inside MANIFEST.MF may not be that obvious to app developers. 3, use a relative jndi-name (a loose term) for job repository datasource in batch subsystem configuration, and this relative jndi-name may be bound to a datasouce declared in application scope. For example, 3.1) admin wants to enforce a global job repository (no per-app job repository), so he can configure jndi-name attribute in the batch subsystem xml snippet: jndi-name = "java:jboss/datasources/ExampleDS" 3.2) admin wants to allow either global or per-app job repository by using relative jndi-name: jndi-name = "datasources/batch-job-repository" 3.2.1) app Foo wants to use global job repository as configured in WildFly server, then do nothing. jberet will just expand the configured jndi-name and use java:jboss/datasources/batch-job-repository as the effective job repository jndi-name. 3.2.2) app Bar wants to use per-application job repository, so Bar can add a resource-ref to its web.xml or application.xml or ejb.xml <resource-ref> <res-ref-name>java:app/env/datasources/batch-job-repository<res-ref-name> <mapped-name>java:jboss/datasources/orderDB</mapped-name> When both app Foo and Bar are running inside WildFly server, Foo uses the global job repository while Bar uses its own job repository (orderDB) without any interference. Any other ideas and suggestions are also welcome. James, feel free to add or correct anything I've missed. Cheng

12 years, 10 months

3
5
0 / 0

Re: [wildfly-dev] JDK 8 build 120 is available on java.net

by Rory O'Donnell Oracle, Dublin Ireland

cc'ing wildfly-dev(a)lists.jboss.org Rgds,Rory On 16/12/2013 09:46, Rory O'Donnell Oracle, Dublin Ireland wrote: > Hi Guys, > > JDK 8 B120 EA Build is now available for download > <http://jdk8.java.net/download.html> & test. > > We are now very late in the release cycle, issues found late may be > postponed to > JDK 9 time frame. Please log all show stopper issues as soon as possible. > > Thanks for your support, Rory > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

12 years, 10 months

1
0
0 / 0

WFLY-2601 and upgrading Hibernate Validator to 5.0.2.Final (not available yet) ...

by Scott Marlow

Hibernate Validator 5.0.2.Final isn't released yet but when it is, I would like to upgrade WF 8 to it. I'd like to see https://hibernate.atlassian.net/browse/HV-838 (deployment class leak) fixed. I am mentioning this here so others aren't surprised if/when a WFLY-2601 pull request is merged. Also see http://lists.jboss.org/pipermail/hibernate-dev/2013-December/010691.html discussion about an ArrayIndexOutOfBoundsException (HV-818) which is still being discussed. Scott

12 years, 10 months

1
0
0 / 0

13 JASPIC tests failing on WildFly

by Arun Gupta

Arjan Tims has added 22 new JASPIC tests to Java EE 7 test suite at: https://github.com/javaee-samples/javaee7-samples/tree/master/jaspic 13 of them are failing with WildFly as shown at: https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil... 21 of these tests are passing on GlassFish as shown at: https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Gla... JASPIC support in WildFly is reported "broken" as mentioned at: https://github.com/arjantijms/jaspic-capabilities-test/commit/7f78a8267b4... Adding a new <security-domain> as mentioned in the above commit message only marginally improves the results. Do you see any basic configuration issue with OOTB WildFly for running these tests ? Arun -- http://blog.arungupta.me http://twitter.com/arungupta

12 years, 10 months

3
4
0 / 0

Push for CORS in WildFly 8

by ssilvert＠redhat.com

Re: https://issues.jboss.org/browse/WFLY-1014 I'd like to request that we take a harder look at getting WFLY-1014 done. This feature allows CORS requests into the HTTP management endpoint. This would solve two problems: 1) The web console must ship with WildFly and must be downloaded from the WildFly instance it is talking to. 2) No other console is allowed to use the HTTP management endpoint. So, a layered product's console can not control its own subsystem. Herald gives a nice overview of what this would mean for the Web Console: http://hpehl.info/independent-jboss-admin-console.html It would be very beneficial for other products as well. Can we get this done? Stan

12 years, 10 months

6
16
0 / 0

JDK 8 build 119 is available on java.net

by Rory O'Donnell Oracle, Dublin Ireland

Hi All, JDK 8 B119 EA Build is now available for download <http://jdk8.java.net/download.html> & test. We are now very late in the release cycle, issues found late may be postponed to JDK 9 time frame. Please log all show stopper issues as soon as possible. Thanks for your support, Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

12 years, 10 months

1
0
0 / 0

Wildfly dir structure - to which extent is it guaranteed to stay as is now?

by Ondrej Zizka

Hi, WRT WFLY-2426 again: Will modules dir structure stay as is for a long term? Talking about major versions of EAP? Recently I asked what's guaranteed to stay, and the reply was, "the management API and the scripts in bin/" Which implicitely tells me that modules/ is not a thing to rely on. Could someone please verify that? Thanks, Ondra PS: We could simply put file-per-layer right into the root dir but releng and others will frown...

12 years, 10 months

2
1
0 / 0

h:fileUpload is not invoking setter

by Arun Gupta

https://github.com/javaee-samples/javaee7-samples/tree/master/jsf/file-up... is a simple sample that demonstrate the usage of newly added h:fileUpload component. The usage is pretty straightforward: <h:form enctype="multipart/form-data"> <h:inputFile value="#{fileUploadBean.file}"/><br/> <h:commandButton value="Upload"/><p/> <h2>File Contents:</h2> <h:outputText value="#{fileUploadBean.text}"/> </h:form> However clicking on the button does not invoke the setFile method on the corresponding bean: public void setFile(Part file) { .... } Any suggestions ? Arun -- http://blog.arungupta.me http://twitter.com/arungupta

12 years, 10 months

1
1
0 / 0

Establishing deployment processor service dependencies

by Richard Achmatowicz

Hi Quick question on establishing service dependencies for deployment unit processors: I have a deployment unit processor DUP1 for a subsystem, which runs in the INSTALL phase and depends on a service X. Although X is installed elsewhere, I want to make sure that X is started before the DUP ever executes as it requires that service for correct operation. Is it the case that the only way to establish this dependency is to: - create a new deployment unit processor DUP2 which runs in the phase immediately preceding INSTALL ( which is POST_MODULE) - use DUP2 to add the dependency to the DeploymentPhaseContext via phaseContext.addToAttachmentList(Attachments.NEXT_PHASE_DEPS, X); Just want to confirm that this is the only way to establish this dependency. Richard

12 years, 10 months

1
0
0 / 0

PR-5551/5552 - version-base.txt

by Ondrej Zizka

Hi all, there's a request for something for static identification of the server in a directory. This comes from JBDS and prehaps other tools (installer, upgrader, ...) The jira is https://issues.jboss.org/browse/WFLY-2426 The discussion on that jira staled, so I created these https://github.com/wildfly/wildfly/pull/5551 https://github.com/wildfly/wildfly/pull/5552 (It's the same thing done in 2 ways.) I suggest to keep the discussion in that jira WFLY-2426 . Is this solution (as described there) acceptable? Even for layered stuff? Max + Rob in the CC. Thanks, Ondra

12 years, 10 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev December 2013