Meet. Brian Stansberry Principal Software Engineer, Red Hat, Inc. June 10, Friday, June 14, 13

Transcription

1

2 Meet Brian Stansberry Principal Software Engineer, Red Hat, Inc. June 10, 2013

3 What s WildFly? New name for the JBoss Application Server project Reduce confusion over the name JBoss WildFly won a public voting election Over 1,800 suggestions Over 200,000 visits to the voting site

4 WildFly and JBoss EAP WildFly: Focus: rapid innovation Major releases every 6 to 9 months JBoss EAP: Focus: stability, long-term support, maintainability WildFly remains the upstream project for EAP But no 1:1 mapping of a WildFly release to each EAP release Once EAP begins to productize a given WF major, no further WF releases in that series

5 Developer Friendly EAP Goal: make it much easier to use EAP in development Way too painful in the past! EAP Alphas freely available for download on jboss.org EAP Betas, CRs and GA releases available for download with a $0 developer subscription Not for production use EAP micro releases (e.g ) require a paid subscription

6 WildFly 8: Key Changes Java EE7 Java SE 7 baseline Integration of Undertow webserver Fine-grained Administrative Access Control Patching Migration from JacORB to the JDK ORB (maybe)

7 WildFly 8: Schedule Monthly releases leading up to Final in November Roughly time-boxed Alpha1 -- May Alpha2 -- this week Alpha3 -- July Beta1 -- August Beta2 -- September CR1 -- October Final -- November 11

8 WF8: What s New in EE7? New APIs WebSocket 1.0 Java API for JSON Processing 1.0 (JSON-P) Batch Application API 1.0 Concurrency Utilities for Java EE 1.0

9 WebSocket /chat ) public class ChatEndpoint public void open(session peer) { sessions.add(peer); public void message(string message, Session client) { for (Session session : sessions) session.getremote().send(message); } public void close(session peer) { sessions.remove(peer); }

10 WF8: What s New in EE7? JAX-RS 2.0 Client API including async processing Server-side Asynchronous HTTP Filters and Interceptors

11 JAX-RS 2.0 Client Client client = ClientFactory.newClient(); WebTarget target = client.target(" Form form = new Form().param("customer", "Bill").param("product", "IPhone 5").param("CC", " "); Response response = target.request().post(entity.form(form)); assert response.getstatus() == 200; Order order = response.readentity(order.class);

12 WF8: What s New in EE7? JMS 2.0 Much improved API JMSContext Encapsulates Connection, Session, MessageProducer In EE, managed and injected by the container Platform default ConnectionFactory JMS objects implement java.lang.autocloseable Delayed delivery, async send JMS @JMSDestinationDefinition

13 JMS 2.0 Client Example // Inject default container connection private JMSContext queue/demoqueue ) private Queue queue; public void sendmessage(string message) { context.createproducer().send(queue, message); }

14 WF8: What s New in EE7? Other API Updates EL 3.0 CDI 1.1 Servlet 3.1 Bean Validation 1.1 JPA 2.1 EJB 3.2 JCA 1.7 JSF 2.2 JTA

15 WF8: What s New in EE7? Optional APIs Following EE7 APIs are now optional and will not be supported in WildFly servers CMP JAXR JAX-RPC JSR-88

16 WF8: Fine Grained Admin Access Control Needed: ability to grant admin users more limited privileges AS7: all admins have superuser privileges Just have to authenticate WildFly 8: Simple role based permission scheme 7 standard roles Map users to roles based on group or username

17 Standard Roles Non-Sensitive Four roles with restricted rights to sensitive data: Monitor: read-only Operator: r/o persistent config; r/w runtime-only start, stop, reload servers pop message off JMS queue, flush DS pool, etc Maintainer: read-write for both config and runtime Deployer: like Maintainer but restricted to application resources

18 Standard Roles Sensitive Three roles with rights to read or modify sensitive data: Administrator: all permissions except cannot access the administrative audit logging system Auditor: r/w access to administrative audit logging r/o for everything else SuperUser: all permissions

19 Scoped Roles User created roles for managed domains Based on the 7 standard roles with an additional constraint Server group scoped role Permissions limited to resources associated with a managed domain server group Host scoped role Permissions limited to a particular domain host

20 Configurability Define what is considered sensitive Potentially sensitive resources, attributes, operations are categorized SOCKET_CONFIG, SECURITY_DOMAIN etc Users can configure whether a category is restricted visibility, read, write Define what is considered an application resource Deployments always are Users can decide about selected other resource

21 WF8: Patching Apply a patch to a single WF installation Standalone server or managed domain host Coordinated rollout across domain not supported in WF 8 Move from one release to another via a patch Patch is staged on filesystem until process is restarted Ability to revert patches, restore previous state CLI is the patch application tool Admin console won t support patching in 8.0

22 WF8: Undertow New webserver project integrated in WildFly 8 Servlet container Server for HTTP management interface HTTP Upgrade /subsystem=undertow instead of /subsystem=web

23 Why Another Webserver? A true non-blocking API (servlet is by itself insufficient) Improved support for modern security standards Upgrade from HTTP to our native protocols future one-port mode Support the latest network protocols naturally and with minimal overhead SPDY, Web Sockets Best possible performance and memory efficiency Handle complex routing use cases a la mod_rewrite Embeddable in standalone process / test environment

24 Why Non-Blocking? Efficiently handles large numbers of connections Required for Java EE7 and Web Sockets More efficient for some targeted use cases Non-blocking file serving via caching Non-blocking proxy implementation Blocking semantics are usually easily mapped on top of a non-blocking server

25 Embedded Undertow public class HelloWorldServer { public static void main(final String[] args) { Undertow server = Undertow.builder().addListener(8080, "localhost").setdefaulthandler(new HttpHandler() public void handlerequest(final HttpServerExchange exchange) throws Exception { exchange.getresponseheaders().put(headers.content_type, "text/plain"); exchange.getresponsesender().send("hello World"); } }).build(); } server.start(); }

26 Embedded Servlet public class ServletServer { public static void main(final String[] args) { try { DeploymentInfo servletbuilder = new DeploymentInfo().setClassLoader(ServletServer.class.getClassLoader()).setContextPath("/myapp").setDeploymentName("test.war ).addservlets( new ServletInfo("MessageServlet", MessageServlet.class).addInitParam("message", "Hello World").addMapping("/*"), new ServletInfo("MyServlet", MessageServlet.class).addInitParam("message", "MyServlet").addMapping("/myservlet"));...

27 Embedded Servlet } }... final ServletContainer container = ServletContainer.Factory.newInstance(); DeploymentManager manager = container.adddeployment(servletbuilder); manager.deploy(); Undertow server = Undertow.builder().addListener(8080, "localhost").sethandler(manager.start()).build(); server.start(); } catch (ServletException e) { throw new RuntimeException(e); }

28 Learn More About Mailing list: undertow-dev IRC on freenode: #undertow Code:

29 Long Term WF WildFly 9 ~ Summer 2014 Reimplement the core management layer Currently much too difficult to write extensions Annotated interfaces, generated implementation Maintain protocol and API compatibility Transactional MSC WildFly? Clean separation between core WildFly and features built on top Better control of feature lifecycle

30 Q&A

31 Get Involved! Downloads: download/ Forums and wiki: community.jboss.org/en/wildfly Docs: WFLY8/Documentation Dev mailing list: IRC on freenode: #wildfly and #wildfly-dev Code: