How to be effective with JBoss Developer StudioMax Andersen
Abstract from JBoss World 2011:
How do you use JBoss Developer Studio effectively while developing applications based on JBoss technology? In this session, Max Rydahl Andersen will cover how you can use pure Eclipse to build multi-module projects, and also how you can make it fit into a Maven world.
Max will explain how you can deploy applications quickly and efficiently into local, remote hosts and even into the cloud.
Red Hat Enterprise Application Platform 6 comes with Maven repository, meaning customers can now easily migrate from JBoss Application Server 7 to Red Hat JBoss Enterprise Application Platform 6. The Maven repository best practices can be used by many Maven-based projects and should be considered as they enable easy upgrades and migrations regardless of using Red Hat JBoss Enterprise Application Platform, Red Hat JBoss SOA Platform, or Red Hat JBoss Data Grid.
In this session, Max Rydahl Andersen will discuss these best practices and their benefits, as well as:
How the Maven repository came to be
What concerns the repository addresses
How a user can best utilize Maven repository
The document discusses developing plug-ins for NetBeans. It describes what a plug-in is, including that it is a JAR file with special manifest entries. It also discusses that plug-ins can expose APIs, depend on other module APIs, and everything is localized. Finally, it provides an overview of the key NetBeans APIs involved in plug-in development, including files/filesystems, data objects, nodes, and lookup patterns.
Enabling White-Box Reuse in a Pure Composition Languageelliando dias
This document discusses enabling white-box reuse in a pure composition language. It introduces a language extension to JPiccola, a composition language, that allows inheritance by generating subclasses at runtime. This enables accessing functionality from existing Java frameworks through inheritance while maintaining JPiccola's scripting style. The implementation generates bytecode for the subclasses by gathering class structure information and redirecting method calls to Piccola services. Examples show generating subclasses and interfaces. The extension integrates well with JPiccola and allows frameworks to be reused through inheritance when needed.
XPages and Java (DanNotes 50th conference, November 2013)Per Henrik Lausten
This document provides an introduction to using Java and beans in XPages. It discusses the differences between POJOs and beans, examples of scoped beans, how to call Java methods from XPages, and debugging techniques. It recommends using Java for as much logic as possible for performance benefits and access to libraries. The presenter is an experienced XPages developer who provides consulting and mentoring.
What we can expect from Java 9 by Ivan KrylovJ On The Beach
Java 9 is currently scheduled to become generally available in less then 1 year. Perhaps now is a good time to have a closer look at language proposals and API changes in Java 9. There are over 70 proposals targeted to Java 9, we will have a looks at some key ones, starting with java modularity. We will look at some breaking changes and ways to develop both short and long term solutions for adoption of new upcoming version of Java.
This document discusses Maven, an open source build automation tool used primarily for Java projects. It introduces some key Maven concepts including plugins, lifecycles, dependencies, profiles, and repositories. Plugins in Maven are similar to tasks in Ant and add functionality by defining goals that are bound to lifecycle phases. The document provides examples of configuring plugins, dependencies, and profiles in Maven projects.
The document discusses a NetBeans plugin development workshop. It introduces questions about why to create NetBeans plugins and the difference between modules and plugins. The workshop will include two exercises exploring the NetBeans IDE and going deeper into how it is built from numerous plugin modules. Resources and references are provided for further learning about the NetBeans plugin platform.
How to be effective with JBoss Developer StudioMax Andersen
Abstract from JBoss World 2011:
How do you use JBoss Developer Studio effectively while developing applications based on JBoss technology? In this session, Max Rydahl Andersen will cover how you can use pure Eclipse to build multi-module projects, and also how you can make it fit into a Maven world.
Max will explain how you can deploy applications quickly and efficiently into local, remote hosts and even into the cloud.
Red Hat Enterprise Application Platform 6 comes with Maven repository, meaning customers can now easily migrate from JBoss Application Server 7 to Red Hat JBoss Enterprise Application Platform 6. The Maven repository best practices can be used by many Maven-based projects and should be considered as they enable easy upgrades and migrations regardless of using Red Hat JBoss Enterprise Application Platform, Red Hat JBoss SOA Platform, or Red Hat JBoss Data Grid.
In this session, Max Rydahl Andersen will discuss these best practices and their benefits, as well as:
How the Maven repository came to be
What concerns the repository addresses
How a user can best utilize Maven repository
The document discusses developing plug-ins for NetBeans. It describes what a plug-in is, including that it is a JAR file with special manifest entries. It also discusses that plug-ins can expose APIs, depend on other module APIs, and everything is localized. Finally, it provides an overview of the key NetBeans APIs involved in plug-in development, including files/filesystems, data objects, nodes, and lookup patterns.
Enabling White-Box Reuse in a Pure Composition Languageelliando dias
This document discusses enabling white-box reuse in a pure composition language. It introduces a language extension to JPiccola, a composition language, that allows inheritance by generating subclasses at runtime. This enables accessing functionality from existing Java frameworks through inheritance while maintaining JPiccola's scripting style. The implementation generates bytecode for the subclasses by gathering class structure information and redirecting method calls to Piccola services. Examples show generating subclasses and interfaces. The extension integrates well with JPiccola and allows frameworks to be reused through inheritance when needed.
XPages and Java (DanNotes 50th conference, November 2013)Per Henrik Lausten
This document provides an introduction to using Java and beans in XPages. It discusses the differences between POJOs and beans, examples of scoped beans, how to call Java methods from XPages, and debugging techniques. It recommends using Java for as much logic as possible for performance benefits and access to libraries. The presenter is an experienced XPages developer who provides consulting and mentoring.
What we can expect from Java 9 by Ivan KrylovJ On The Beach
Java 9 is currently scheduled to become generally available in less then 1 year. Perhaps now is a good time to have a closer look at language proposals and API changes in Java 9. There are over 70 proposals targeted to Java 9, we will have a looks at some key ones, starting with java modularity. We will look at some breaking changes and ways to develop both short and long term solutions for adoption of new upcoming version of Java.
This document discusses Maven, an open source build automation tool used primarily for Java projects. It introduces some key Maven concepts including plugins, lifecycles, dependencies, profiles, and repositories. Plugins in Maven are similar to tasks in Ant and add functionality by defining goals that are bound to lifecycle phases. The document provides examples of configuring plugins, dependencies, and profiles in Maven projects.
The document discusses a NetBeans plugin development workshop. It introduces questions about why to create NetBeans plugins and the difference between modules and plugins. The workshop will include two exercises exploring the NetBeans IDE and going deeper into how it is built from numerous plugin modules. Resources and references are provided for further learning about the NetBeans plugin platform.
Intelligent Projects with Maven - DevFest IstanbulMert Çalışkan
The document discusses Maven, an open source build automation tool used primarily for Java projects. It provides an overview of Maven's key features like dependency management, build lifecycles, and the project object model (POM). The presentation also demonstrates how to create a basic Maven project, configure dependencies and repositories, and manage multi-module builds.
This document provides an overview and summary of the Maven build automation tool:
- Maven is a project management and comprehension tool that handles builds, dependencies, documentation, and reporting for Java projects. It aims to make builds easy and standardized.
- Core Maven concepts include the Project Object Model (POM), the build lifecycle of phases and goals, and dependency management through repositories.
- The POM defines a project and its relationships. The build lifecycle standardizes the build process through phases like compile, test, package. Dependencies are resolved through a repository system.
- Maven handles transitive dependencies, dependency scopes, version ranges, andSNAPSHOT versions to simplify builds and dependency management
The document discusses creating a strong documentation culture. It notes that everyone reads documentation for various reasons such as first contact, education, support, troubleshooting, and reference. Great documentation has different types of content including tutorials for new users, topic guides for conceptual understanding, reference materials, and troubleshooting guides. Documentation should be written by developers and be "fractal" in its level of detail. While tools are not most important, good documentation tools like Sphinx and Read the Docs can help. The overall aim is to establish a culture where developers recognize the importance of documentation.
JMP402 Master Class: Managed beans and XPages: Your Time Is NowRussell Maher
Russell Maher presented on using managed beans in XPages applications. He began with high-level concepts on what managed beans are and how they are configured and used. He then walked through creating a simple "first" managed bean as an example. Maher discussed when managed beans make sense to use, such as for complex logic or persistence needs. The presentation continued with building an "audit bean" for a demo application and discussed debugging and documentation of managed beans.
Java 7 Modularity: a View from the Gallerynjbartlett
The document discusses Java modularity and Project Jigsaw. It summarizes that Project Jigsaw aims to modularize the Java Development Kit (JDK) to address issues like its large size, slow startup times, and difficulties evolving APIs and managing dependencies. It also discusses the potential for module systems like Jigsaw and OSGi to fragment the Java ecosystem if they are not compatible.
An introduction to the Java Platform Module System (JPMS). This talk is from April 2017, before the Java SE 9 release, so the final details may be subtly different, particularly once a standard becomes established for module names.
This document provides an overview of managed beans in IBM Domino applications. It discusses key concepts such as what managed beans are, how they are configured and used, and when they make sense to use over traditional server-side JavaScript. It then outlines steps to create a basic managed bean, including creating the Java class, adding properties and getters/setters, configuring in faces-config.xml, and using the bean in an XPage. The document also covers debugging managed beans and presents an example application where managed beans would be well suited to address complexity and persistence needs.
1. Maven is a build automation tool that manages Java projects and dependencies. It uses a pom.xml file to define build configuration including dependencies, plugins, and lifecycle phases.
2. A Maven project consists of goals bound to phases in a lifecycle. Common goals include compile, test, and package. Maven coordinates including groupId, artifactId, and version uniquely identify dependencies.
3. Maven downloads dependencies from repositories. It publishes artifacts to the local repository for sharing between projects. Artifacts include JAR files and pom.xml files.
A slide deck presenting the highlights of the NetBeans IDE 7 release, including each of its minor releases, 7.1, 7.1.1, 7.2, 7.2.1, 7.3, 7.3.1, and 7.4, in the context of the IDE's complete feature set.
Maven is a build tool that provides dependency management, compilation, testing and packaging functionality. It handles dependency resolution by allowing developers to specify dependencies in a pom.xml file. Maven will then download the dependencies from repositories. Maven also provides standardized project structures and build lifecycles that allow projects to be built in a predictable, repeatable manner.
Writing concurrent code that is also correct is unbelievably hard. Naturally, humanity has developed a number of approaches to handle concurrency in the code, starting from basic threads that follow the hardware way to do concurrency to higher level primitives like fibers and work-stealing solutions. But which approach is the best for you? In this session, we'll take a look at a simple concurrent problem and solve it using different ways to manage concurrency: threads, executors, actors, fibers, monadic code with completable futures. All these approaches are different from the simplicity, readability, configuration and management point of view. Some scenarios are better modelled with threads, while sometimes you're better off with actors. We'll discuss the benefits of each approach and figure out when it's worth pursuing in your project.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2vgN64e.
Dan Lawesson talks about his experience migrating Speedment to Java 9. He covers examples such as test frameworks failing and dependencies needing to be reworked to accommodate the stricter Java 9 modularization. Filmed at qconnewyork.com.
Dan Lawesson is CSO at Speedment. Before joining the Speedment Team he has been building IoT systems in the automotive industry and also been working as a Java examiner at the Linkoping University. He is an experienced speaker at events like ISICS (Information Systems for Industrial Control and Supervision) workshops, JUGs and meetups.
The document discusses the Java Community Process (JCP) and the future of Java. It provides an overview of the JCP, including its goals of open standards, compatibility, and broad community involvement. It outlines several recent and upcoming Java specifications being developed through the JCP, and encourages developers to get involved in JSR expert groups, hackathons, and other community events to help shape the future of Java.
Based on the example of the XWiki Open Source project (http://xwiki.org) this session will describe a number of practices to improve the quality of a Java project. Also, it will show how to implement these practices so that they are automatically checked and enforced. Some examples include: *How to make sure your project does not break binary compatibility unintentionally and, more generally, how to successfully evolve an API without breaking your users; *How to manage the JAR hell and avoid duplication of classes in your application at runtime; *How to automatically control the test coverage and the associated policies; *How to automate functional testing of web applications and how to avoid false-positives that plague any project..
A flash lecture given at the JJTV Tool Night #4 on 6 November, 2012.
The full lecture video (in Hebrew) can be found at http://www.youtube.com/watch?v=ozl6oBmAj1Y
The document discusses the messy and buggy state of the DOM across browsers and strategies for writing cross-browser JavaScript code. It notes that nearly every DOM method has bugs or inconsistencies in some browsers. It then covers strategies like feature detection, graceful fallback for missing features, simulating features via workarounds, monitoring for regressions, and having a robust test suite to prevent regressions in one's own code. The overall message is that the DOM is messy and one needs to "know your enemies" by thoroughly testing code in all target browsers.
Apache maven and its impact on java 9 (Java One 2017)Robert Scholte
Maven is a build tool that manages projects and dependencies. It aims to make the build process easy and provide a uniform system. With Java 9, Maven faces challenges due to the module system's differences from the classpath. Specifically, the modulepath does not support all file types like the classpath. This causes issues for Maven which relies on dependencies being on the classpath. Additionally, automatic modules generated from JAR files can cause problems for projects. Maven cannot directly generate module descriptors but tools like Jdeps can assist with initial descriptors. Overall, while challenges exist, Maven can still be used for most projects with Java 9.
The document discusses Groovy's capabilities for working with XML, including parsing, manipulating, and generating XML. Groovy provides classes like XmlParser, XmlSlurper, and DOMCategory that allow working with XML in a more concise way compared to traditional Java XML APIs. Groovy also simplifies working with XML namespaces. The document provides examples demonstrating how to parse XML, extract data, update XML, and generate XML using Groovy's XML features.
This presentation provides a comprehensive overview of Maven 3 including lifecycles and a detail of the default lifecycle and the associated phases within.
Java EE 6 & GlassFish V3 - Alexis Moussine-Pouchkine - May 2010JUG Lausanne
GlassFish v3 is the latest version of the GlassFish application server which implements the full Java EE 6 specification; it includes new features like Java API for RESTful Web Services (JAX-RS 1.1), Contexts and Dependency Injection for Java EE (CDI 1.0), and Bean Validation 1.0. GlassFish v3 provides an open source, modular, and extensible Java EE application server platform that can be used for cloud computing and embedded applications. Going forward, Oracle will continue to develop GlassFish as an open source project while providing commercial support.
Performance Tuning: Pulling a Rabbit From a Hat - Atlassian Summit 2010Atlassian
The document discusses ways to improve application performance at Atlassian. It describes how Atlassian performs performance testing on its software and reports results to developers. It also outlines several things individuals can do to boost performance, including upgrading to newer Java versions, improving hardware, removing virtualization overhead, and tuning garbage collection settings. Atlassian aims to continuously fix performance issues through testing and prioritizing performance in software releases.
JIRA Studio: Development in the Cloud - Atlassian Summit 2010Atlassian
1. Razorfish is a global digital agency with over 1,500 professionals in 21 cities worldwide. It provides full-service digital services including web design, development, and marketing.
2. Razorfish uses a customer-centric agile model where user stories drive all aspects of a project from planning to testing. It employs 3-week iteration cycles consisting of planning and implementation phases.
3. Each iteration includes feature review, task assignment, coding, testing, code review, and refinement for continuous improvement. This embraces change and allows for building in increments to achieve the best results.
Intelligent Projects with Maven - DevFest IstanbulMert Çalışkan
The document discusses Maven, an open source build automation tool used primarily for Java projects. It provides an overview of Maven's key features like dependency management, build lifecycles, and the project object model (POM). The presentation also demonstrates how to create a basic Maven project, configure dependencies and repositories, and manage multi-module builds.
This document provides an overview and summary of the Maven build automation tool:
- Maven is a project management and comprehension tool that handles builds, dependencies, documentation, and reporting for Java projects. It aims to make builds easy and standardized.
- Core Maven concepts include the Project Object Model (POM), the build lifecycle of phases and goals, and dependency management through repositories.
- The POM defines a project and its relationships. The build lifecycle standardizes the build process through phases like compile, test, package. Dependencies are resolved through a repository system.
- Maven handles transitive dependencies, dependency scopes, version ranges, andSNAPSHOT versions to simplify builds and dependency management
The document discusses creating a strong documentation culture. It notes that everyone reads documentation for various reasons such as first contact, education, support, troubleshooting, and reference. Great documentation has different types of content including tutorials for new users, topic guides for conceptual understanding, reference materials, and troubleshooting guides. Documentation should be written by developers and be "fractal" in its level of detail. While tools are not most important, good documentation tools like Sphinx and Read the Docs can help. The overall aim is to establish a culture where developers recognize the importance of documentation.
JMP402 Master Class: Managed beans and XPages: Your Time Is NowRussell Maher
Russell Maher presented on using managed beans in XPages applications. He began with high-level concepts on what managed beans are and how they are configured and used. He then walked through creating a simple "first" managed bean as an example. Maher discussed when managed beans make sense to use, such as for complex logic or persistence needs. The presentation continued with building an "audit bean" for a demo application and discussed debugging and documentation of managed beans.
Java 7 Modularity: a View from the Gallerynjbartlett
The document discusses Java modularity and Project Jigsaw. It summarizes that Project Jigsaw aims to modularize the Java Development Kit (JDK) to address issues like its large size, slow startup times, and difficulties evolving APIs and managing dependencies. It also discusses the potential for module systems like Jigsaw and OSGi to fragment the Java ecosystem if they are not compatible.
An introduction to the Java Platform Module System (JPMS). This talk is from April 2017, before the Java SE 9 release, so the final details may be subtly different, particularly once a standard becomes established for module names.
This document provides an overview of managed beans in IBM Domino applications. It discusses key concepts such as what managed beans are, how they are configured and used, and when they make sense to use over traditional server-side JavaScript. It then outlines steps to create a basic managed bean, including creating the Java class, adding properties and getters/setters, configuring in faces-config.xml, and using the bean in an XPage. The document also covers debugging managed beans and presents an example application where managed beans would be well suited to address complexity and persistence needs.
1. Maven is a build automation tool that manages Java projects and dependencies. It uses a pom.xml file to define build configuration including dependencies, plugins, and lifecycle phases.
2. A Maven project consists of goals bound to phases in a lifecycle. Common goals include compile, test, and package. Maven coordinates including groupId, artifactId, and version uniquely identify dependencies.
3. Maven downloads dependencies from repositories. It publishes artifacts to the local repository for sharing between projects. Artifacts include JAR files and pom.xml files.
A slide deck presenting the highlights of the NetBeans IDE 7 release, including each of its minor releases, 7.1, 7.1.1, 7.2, 7.2.1, 7.3, 7.3.1, and 7.4, in the context of the IDE's complete feature set.
Maven is a build tool that provides dependency management, compilation, testing and packaging functionality. It handles dependency resolution by allowing developers to specify dependencies in a pom.xml file. Maven will then download the dependencies from repositories. Maven also provides standardized project structures and build lifecycles that allow projects to be built in a predictable, repeatable manner.
Writing concurrent code that is also correct is unbelievably hard. Naturally, humanity has developed a number of approaches to handle concurrency in the code, starting from basic threads that follow the hardware way to do concurrency to higher level primitives like fibers and work-stealing solutions. But which approach is the best for you? In this session, we'll take a look at a simple concurrent problem and solve it using different ways to manage concurrency: threads, executors, actors, fibers, monadic code with completable futures. All these approaches are different from the simplicity, readability, configuration and management point of view. Some scenarios are better modelled with threads, while sometimes you're better off with actors. We'll discuss the benefits of each approach and figure out when it's worth pursuing in your project.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2vgN64e.
Dan Lawesson talks about his experience migrating Speedment to Java 9. He covers examples such as test frameworks failing and dependencies needing to be reworked to accommodate the stricter Java 9 modularization. Filmed at qconnewyork.com.
Dan Lawesson is CSO at Speedment. Before joining the Speedment Team he has been building IoT systems in the automotive industry and also been working as a Java examiner at the Linkoping University. He is an experienced speaker at events like ISICS (Information Systems for Industrial Control and Supervision) workshops, JUGs and meetups.
The document discusses the Java Community Process (JCP) and the future of Java. It provides an overview of the JCP, including its goals of open standards, compatibility, and broad community involvement. It outlines several recent and upcoming Java specifications being developed through the JCP, and encourages developers to get involved in JSR expert groups, hackathons, and other community events to help shape the future of Java.
Based on the example of the XWiki Open Source project (http://xwiki.org) this session will describe a number of practices to improve the quality of a Java project. Also, it will show how to implement these practices so that they are automatically checked and enforced. Some examples include: *How to make sure your project does not break binary compatibility unintentionally and, more generally, how to successfully evolve an API without breaking your users; *How to manage the JAR hell and avoid duplication of classes in your application at runtime; *How to automatically control the test coverage and the associated policies; *How to automate functional testing of web applications and how to avoid false-positives that plague any project..
A flash lecture given at the JJTV Tool Night #4 on 6 November, 2012.
The full lecture video (in Hebrew) can be found at http://www.youtube.com/watch?v=ozl6oBmAj1Y
The document discusses the messy and buggy state of the DOM across browsers and strategies for writing cross-browser JavaScript code. It notes that nearly every DOM method has bugs or inconsistencies in some browsers. It then covers strategies like feature detection, graceful fallback for missing features, simulating features via workarounds, monitoring for regressions, and having a robust test suite to prevent regressions in one's own code. The overall message is that the DOM is messy and one needs to "know your enemies" by thoroughly testing code in all target browsers.
Apache maven and its impact on java 9 (Java One 2017)Robert Scholte
Maven is a build tool that manages projects and dependencies. It aims to make the build process easy and provide a uniform system. With Java 9, Maven faces challenges due to the module system's differences from the classpath. Specifically, the modulepath does not support all file types like the classpath. This causes issues for Maven which relies on dependencies being on the classpath. Additionally, automatic modules generated from JAR files can cause problems for projects. Maven cannot directly generate module descriptors but tools like Jdeps can assist with initial descriptors. Overall, while challenges exist, Maven can still be used for most projects with Java 9.
The document discusses Groovy's capabilities for working with XML, including parsing, manipulating, and generating XML. Groovy provides classes like XmlParser, XmlSlurper, and DOMCategory that allow working with XML in a more concise way compared to traditional Java XML APIs. Groovy also simplifies working with XML namespaces. The document provides examples demonstrating how to parse XML, extract data, update XML, and generate XML using Groovy's XML features.
This presentation provides a comprehensive overview of Maven 3 including lifecycles and a detail of the default lifecycle and the associated phases within.
Java EE 6 & GlassFish V3 - Alexis Moussine-Pouchkine - May 2010JUG Lausanne
GlassFish v3 is the latest version of the GlassFish application server which implements the full Java EE 6 specification; it includes new features like Java API for RESTful Web Services (JAX-RS 1.1), Contexts and Dependency Injection for Java EE (CDI 1.0), and Bean Validation 1.0. GlassFish v3 provides an open source, modular, and extensible Java EE application server platform that can be used for cloud computing and embedded applications. Going forward, Oracle will continue to develop GlassFish as an open source project while providing commercial support.
Performance Tuning: Pulling a Rabbit From a Hat - Atlassian Summit 2010Atlassian
The document discusses ways to improve application performance at Atlassian. It describes how Atlassian performs performance testing on its software and reports results to developers. It also outlines several things individuals can do to boost performance, including upgrading to newer Java versions, improving hardware, removing virtualization overhead, and tuning garbage collection settings. Atlassian aims to continuously fix performance issues through testing and prioritizing performance in software releases.
JIRA Studio: Development in the Cloud - Atlassian Summit 2010Atlassian
1. Razorfish is a global digital agency with over 1,500 professionals in 21 cities worldwide. It provides full-service digital services including web design, development, and marketing.
2. Razorfish uses a customer-centric agile model where user stories drive all aspects of a project from planning to testing. It employs 3-week iteration cycles consisting of planning and implementation phases.
3. Each iteration includes feature review, task assignment, coding, testing, code review, and refinement for continuous improvement. This embraces change and allows for building in increments to achieve the best results.
The Information Radiator: Creating Awesome Wallboards - Atlassian Summit 2010...Atlassian
The document describes an information radiator, which is a large display that continuously shows critical team information in an easy to understand format. It discusses what types of information are useful to include, such as performance metrics and fun facts. The document then proposes building an information radiator as a JIRA plugin that can pull information from JIRA, Bamboo, and other tools and display it in configurable dashboards. It demos an early prototype and outlines plans to create a polished plugin to make information radiators easy for any team to set up within JIRA.
Dev Tools State of the Union (Part I) - Atlassian Summit 2010Atlassian
The document provides an overview of updates to JIRA and GreenHopper. Key points include doubling the development team for JIRA, releasing versions every 3-4 months, and growing the customer base for JIRA and GreenHopper to over 34,000 and 10,700 respectively. New features for JIRA include improved user experience and dashboards/gadgets. GreenHopper 5 provides enhanced support for Scrum and Kanban workflows through planning, task, and chart boards.
Going Agile: Brought to You by the Public Broadcasting System - Atlassian Sum...Atlassian
This document summarizes PBS's transition to an agile development process using Atlassian tools. It describes PBS's organizational structure and technical environment. It then outlines the challenges that led PBS to adopt agile practices like user stories, iteration planning, stand-up meetings, code reviews, and documentation. Key tools implemented include Jira, Confluence, Bamboo, TestLink, and Crowd. The document concludes that these changes improved visibility, transparency, and efficiency compared to the previous process.
JIRA 4 Partner Seminar will cover the new features of JIRA 4 including OpenSocial Dashboards, Dynamic GUI, JIRA Query Language (JQL), and GreenHopper 4.0. The seminar agenda includes introductions, overviews of the new features and enhancements, demonstrations of dashboards and JQL, a session on GreenHopper, and time for questions. Key facts about JIRA 4 include per user pricing, starter licenses available to donate proceeds to charity, and over 800 issues resolved in the new version.
Building Atlassian Plugins with Groovy - Atlassian Summit 2010 - Lightning TalksAtlassian
Groovy is a dynamic language that runs on the JVM and provides features like closures, builders, and domain specific languages that make developing Atlassian plugins more productive compared to Java. Groovy code is more concise and readable than equivalent Java code for many tasks like iterating over lists and parsing XML. Dynamic typing in Groovy does not preclude robust IDE support and tooling. Groovy can leverage Java libraries and is a fully-featured language suitable for professional development.
Auditing Your Build and Release Infrastructure - Atlassian Summit 2010 - Ligh...Atlassian
The document discusses auditing your build and release processes. It recommends defining your build process, measuring your infrastructure performance, setting up controlled builds, ensuring sufficient build agent capacity, treating the build as your product, and communicating with relevant stakeholders. The overall goal is to lay the groundwork, quantify metrics, establish controls, allocate resources, take ownership, and gather feedback around your organization's software development builds.
From the Atlassian Labs: FedEx Champions - Atlassian Summit 2010 - Lightning ...Atlassian
Atlassian's FedEx Days program allows developers to work on self-directed projects for 24 hours to address issues or ideas related to Atlassian's products. Some benefits include improving morale, fostering creativity, and potentially developing innovations that could be incorporated into products. Examples are given of projects like adding broken build tracking to Bamboo, improving FishEye's side-by-side diff view, and developing a JIRA plugin for video capture. The program is said to drive innovation and be highly beneficial for both developers and Atlassian.
Kaizen With GreenHopper: Visualising Agile & Kanban StorywallsCraig Smith
Best practices and lessons learned from a real-world software development team. Suncorp adopted a Kanban-based lean software development approach using JIRA, Greenhopper and other Atlassian tools.
Key Takeaways:
* Overview of agile software techniques
* How Kanban can be applied to software development, maintenance and support
* How to ensure kaizen (improvement) is part of your dev process.
This document provides an overview of JIRA workflows including:
- Key terminology used in JIRA workflows like statuses, transitions, conditions, and validators
- Examples of modifying the default JIRA workflow versus building a new one from scratch
- Tips for visualizing your workflow needs before building, identifying required customizations, planning transitions, and testing the completed workflow
- An example of adding an approval step to an existing workflow
JIRA Performance Testing in Pictures - Edward Bukoski Michael MarchAtlassian
This document summarizes a presentation about performance testing tools used at JP Morgan Chase for their JIRA instance over several years. It discusses the tools they used - Load Runner, JMeter, nGrinder, and more recently Gatling with InfluxDB and Grafana. It provides a scorecard comparing the tools and demonstrations of using Gatling and viewing results in Grafana. Key takeaways are to pick the right tools for the job, know your constraints and goals, and reach out for help from Atlassian and partners.
The document provides information on using Atlassian JIRA and GreenHopper for agile project management. It describes GreenHopper as a plugin for JIRA that allows issues in JIRA to be displayed and organized in different modes for planning, work, and reporting. It then covers how to use GreenHopper for Scrum and Kanban workflows, including configuring boards, columns, statuses and versions to support agile planning, tracking and reporting.
JIRA is a software tool. JIRA lets you prioritize, assign, track, report and audit your ‘issues’, from software bugs and helpdesk tickets to project tasks and change requests.
The document provides an agenda for a presentation on JIRA. The agenda includes explaining what JIRA is, discussing JIRA concepts and features, explaining why JIRA is useful, demonstrating how to use JIRA live, and holding a question and answer session. Sections of the presentation will cover topics like what JIRA is used for, how issues, projects and subtasks are organized in JIRA, example implementations of JIRA in different contexts, and key features and benefits of the software.
Similar to 5 Thing You're Not Doing, 4 Things You Should Stop Doing & 3 Things You Should Keep Doing in Your Plugin - Atlassian Summit 2010 - Lightning Talks
The document provides guidance and best practices for deploying a Joomla site to a live server, including:
1) Using a development/staging site to test changes before deploying live to avoid issues.
2) Transferring site files and database from the development to live server.
3) Adjusting configuration settings like disabling unused extensions and enabling caching for performance.
4) Backing up the live site regularly using tools like AkeebaBackup to prevent data loss.
This document discusses building progressive web apps (PWAs) using Google Web Toolkit (GWT). It defines PWAs and explains how GWT can be used to build them. It provides recipes for incorporating responsiveness, fast loading, offline capabilities, and data storage into GWT apps to make them more progressive. Finally, it announces a GWT archetype that generates projects with tools and configurations to build PWAs using GWT and the Polymer library.
Max Voloshin - "Organization of frontend development for products with micros...IT Event
While our product was growing our team came to need to implement microservices. Later it became obvious that our approaches on organization of frontend development should be rethought and significantly improved.
The report contains our team's solutions for simple and comfortable frontend product development with microservices. Also, this talk is about how we along with the way updated frontend framework, separated frontend and backend, solved internalization problem and started using Docker for front end tasks.
This document discusses approaches to mobile development, including web mobile, native, and hybrid approaches. It then covers specific mobile development frameworks and tools that can be used with IBM Notes/Domino including the XPages Extension Library mobile controls, Bootstrap, jQuery Mobile, HTML5 offline capabilities, PhoneGap/Apache Cordova, Titanium, and IBM Worklight. IBM Worklight is described as providing services to augment PhoneGap, including tools like Worklight Studio, the Worklight Application Center, capabilities of the Worklight runtime and server, and the Worklight Console.
AtlasCamp 2011 - Five Strategies to Accelerate Plugin Developmentmrdon
The document outlines five strategies for accelerating plugin development: 1) Use Speakeasy to validate plugin ideas before building, 2) Define interactions with page objects for testing, 3) Optimize the development loop with the SDK, 4) Reuse functionality with the Atlassian UI (AUI) framework, and 5) Encourage user feedback through tools like JIRA Mobile Connect. It also discusses the potential for "remote plugins" that could run on a server instead of requiring installation in each product.
Unlearning and Relearning jQuery - Client-side Performance OptimizationJon Dean
The document discusses client-side performance optimization when using jQuery. It explains that perceived performance is important to users and outlines some techniques to improve performance such as reducing the number of server requests, using sprites, and compressing files. It discusses why jQuery is commonly used, noting benefits like dealing with browser inconsistencies and writing less code. It also explains some key jQuery concepts like DOM ready, which runs code when the DOM is ready rather than waiting for all assets to load like window.onload. The document provides tips on when to use DOM ready versus onload to optimize loading of JavaScript code.
The document provides steps to create JSR-168/JSR-286 portlets using Google Web Toolkit (GWT) with Liferay Portal. It outlines installing necessary software including Eclipse, GWT, Java JDK, Ant, and Liferay Portal. It then describes creating a Liferay project and portlet, adding GWT to the portlet, and deploying the portlet on Liferay Portal.
Plone Futures, Plone Conference 2016 Keynote by Eric SteeleT. Kim Nguyen
Eric will cover what's in store for Plone 5.1 and beyond, including the work that's been done on plone.server and Mosaic. He will describe the multiple paths of modernizing the stack that are currently underway. This would move us right into the thick of the modern era of web development - with multiple front end implementations communicating with a RESTful back end.
This document summarizes Plone's future plans and directions. Key points include:
- Plone 5.1 will focus on bug fixes and optimizations rather than new features.
- Future releases will improve customization options, documentation/training, and code quality.
- Plone is moving towards a "headless" model where the content management is separated from presentation, to better support mobile and other frontends.
- This will involve developing separate teams for the REST API, frontend interfaces, and backend services using newer technologies like asyncio and React.
- The goal is a cleaner, simplified and future-proofed Plone optimized for a headless/decoupled approach.
AUSPC 2011: How we did it: NothingButSharePoint.comJeremy Thake
Jeremy Thake presented on how the global community website NothingButSharePoint.com was built on the SharePoint 2010 platform. Key aspects included migrating existing content from other systems, using SharePoint 2010's web content management and publishing features, developing extensions like for comments and analytics, and leveraging tools like Visual Studio and PowerShell for implementation. Challenges included working with limitations of SharePoint 2010 and coordinating developers and designers. Lessons learned were about setting clear expectations, plans, and communication across the team.
This document discusses various topics related to developing web apps, including HTML5, responsive design, touch events, offline capabilities, and debugging tools. It provides links to resources on HTML5 features like media queries, SVG, web workers, and the page visibility API. It also covers techniques for adapting content like responsive web design, progressive enhancement, and server-side adaptation. Mobile browser stats and popular devices on Douban are mentioned. Frameworks like Bootstrap and tools like Weinre for debugging mobile apps are referenced.
This document discusses various techniques for making web applications work offline and with unreliable network connections, including:
- The application cache manifest which allows specifying cached resources to work offline
- Issues with the current manifest specification and potential enhancements
- The window.applicationCache API for caching resources and monitoring cache status
- Detecting online/offline status using the navigator.onLine property
In 3 sentences or less, it summarizes approaches for offline web applications using the application cache manifest, applicationCache API, and navigator.onLine property.
This document outlines an agenda for a web performance training course. It introduces key concepts like why performance matters, how to define and measure performance metrics, and how to identify and address performance problems. It provides numerous links to tools and resources for auditing site performance, establishing performance budgets, monitoring performance over time, and optimizing code and assets to improve loading speed. The goal is to help attendees learn how to evaluate the performance of their sites and make them faster.
Web Test Automation Framework - IndicThreads ConferenceIndicThreads
This presentation discusses building a web test automation framework using open source tools including Google WebDriver. It covers understanding the current testing scenario, identifying pain points, an overview of the proposed framework including its architecture, onboarding process, and what was achieved. The framework uses a page object model and testNG reporting. It allows for structured, reusable, and multi-contributor automated testing across browsers and operating systems.
Top Ten Tips for HTML5/Mobile Web DevelopmentSimon Guest
The document provides top 10 tips and tricks for HTML5/mobile web development. It discusses whether to use a mobile web or hybrid approach and recommends considering features like geolocation and offline support when making that decision. It also covers setting up development and testing environments, using client-side JavaScript for navigation and performance, enabling offline support, choosing UI frameworks, handling maps, non-standard elements, packaging, authentication, and optimizing for performance.
I. Spoon is a browser extension and server platform that allows apps to be run from Spoon's servers and virtualized in Spoon's ecosystem. It provides a browser sandbox and app library.
II. Mouseflow is a click and movement analytics tool that generates heatmaps showing where users click and move their mouse on websites. It can be installed via JavaScript code or a WordPress plugin.
III. The document discusses Internet Explorer compatibility issues and introduces the new X-UA-Compatible meta tag to control document rendering mode in IE versions.
I. Spoon is a browser extension and server platform that allows apps to be run from Spoon's servers and virtualized in Spoon's ecosystem. It provides a browser sandbox and app library.
II. Mouseflow is a click and movement analytics tool that generates heatmaps showing where users click and move their mouse on websites. It can be installed via JavaScript code or a WordPress plugin.
III. The document discusses Internet Explorer compatibility issues and introduces the new X-UA-Compatible meta tag to control document rendering mode in IE versions.
The document provides an overview of ExtJS, a JavaScript framework. It discusses trends in JavaScript like single page applications and MVC architecture. It then defines ExtJS, noting it is an open source framework developed by Sencha with rich UI components and support for HTML5. Some key benefits of ExtJS are discussed, like cross-browser support, powerful build tools, and accessibility features. The document demonstrates a simple "Hello World" app in ExtJS and covers core concepts like components, data packages, layouts and containers. It also lists additional ExtJS topics like localization, drag and drop, theming and MVVM.
Similar to 5 Thing You're Not Doing, 4 Things You Should Stop Doing & 3 Things You Should Keep Doing in Your Plugin - Atlassian Summit 2010 - Lightning Talks (20)
We aim to celebrate women every day, but we’re taking today to give special recognition to womxn at Atlassian continue who inspire and lead.
For #InternationalWomensDay, we asked Atlassians to nominate and recognize amazing womxn at Atlassian who inspire them, challenge them, and truly represent Atlassian values.
Ever wondered what Atlassian engineers do in their 20% time? Join Forge engineering lead Tim Pettersen on a lightning tour of how Forge is being used inside Atlassian. Attendees will get a rare view into some of the apps, tools, and tweaks we’ve built internally on top of Forge in the spirit of dogfooding and innovation. Come along and be inspired with some great ideas for improving and automating your own teams' workflows!
Let's Build an Editor Macro with Forge UIAtlassian
Race out of the gate with Forge UI: a new way of building UI extensions for Atlassian products. In this session, Forge UI Developer Experience lead Peter Gleeson will demonstrate how build an Editor macro from scratch! Attendees will learn about Forge foundational concepts such as the FaaS dev loop, Forge CLI, and how to construct UIs from Forge UI components.
This session provides a great introduction to the Forge platform for any developer looking to get productive with editor apps and Forge UI.
In the words of Jeff Atwood: “JavaScript is the lingua franca of the web”. It’s also the first language we’ve chosen to support in Forge. In this session, Forge engineer Shorya Raj will walk through the Node.js isolate based runtime you’ll be using to write apps for Forge.
Attendees will learn about the unique features of the Forge JavaScript Runtime, such as automatic authentication and tenant context management. Shorya will also cover the differences between the Runtime, conventional browser, and Node.js APIs.
Developers or attendees with some programming experience will get the most out of this session.
Forge UI: A New Way to Customize the Atlassian User ExperienceAtlassian
UI extensibility is an integral part of Atlassian's ecosystem story. In cloud, traditionally this has been accomplished with the humble iframe. In this session you will learn about Forge UI, an additional and innovative way to build visual apps for Atlassian products.
Join Product Manager Simon Kubica and Senior Developer Michael Oates from the Forge team in exploring the underlying concepts and technology powering Forge UI, and learn how it will unlock exciting new opportunities in our ecosystem.
This document discusses using triggers to automate actions in Forge apps. It begins with an overview of triggers and then discusses:
- Product triggers that are triggered by events in Atlassian products like Jira, Confluence etc.
- Web triggers that are triggered by HTTP requests to a Forge function.
- How to authenticate and make requests to external services like Opsgenie from Forge functions in response to triggers.
- Demos of building a Forge app that responds to Jira issue creation by assigning the issue and notifying Opsgenie.
The document provides details on the event payload formats, making authenticated requests, and deploying/managing the Forge app lif
Observability and Troubleshooting in ForgeAtlassian
The document discusses the evolution of software development from bare metal servers to virtualization, containers, and serverless functions. It notes how debugging and observability have become more difficult as software moves to remote "somebody else's computer" environments. The author introduces Forge as Atlassian's solution for providing developers a declarative language and best-in-class experience for building user interfaces on serverless infrastructure, including features for debugging, monitoring, and security.
Trusted by Default: The Forge Security & Privacy ModelAtlassian
Security and trust have become increasingly important requirements for our customers in Cloud. We’re working to make it easier for you to build and maintain secure apps for Atlassian products.
In this session, Engineering Team Lead Dugald Morrow and Principal Product Manager Joël Kalmanowicz will explain how security and trust have been baked into the Forge framework and the benefits the platform can offer you and your users. Learn how much less work it can be to build trusted apps customers will love on Forge by going deep on the safeguards we’re putting in place.
Developers or attendees with some software security experience will get the most out of this session.
Designing Forge UI: A Story of Designing an App UI SystemAtlassian
Creating apps with Forge and its UI frontend components is now easier than ever. Join Senior Designer Allard van Helbergen and Product Manager Josephine Lee as they walk through the story of designing Forge UI.
What is a declarative UI and why did we choose this paradigm? What are all the considerations that go into defining the set of components to build apps with? And how do you make ‘creating apps’ simple? Walk away understanding the foundations of Forge, how all the different components work together, and where Forge UI is headed in the future.
After a day of learning about the exciting features of Forge, get ready for a peek under the hood to discover how it’s all implemented. Join Forge Architect Patrick Streule as he goes deep on topics such as Forge FaaS infrastructure, the internal workings of tenant isolation, and automatic authentication.
Attendees will also get a glimpse of some features we’re looking at building into the future of Forge, such as a serverless data store for apps and more!
Access to User Activities - Activity Platform APIsAtlassian
How do you stay on top of your work when it is scattered across multiple Atlassian products?
"If only there was a single place where I could see all my activity..." - sounds familiar?
We are going to provide you an insight into what lead to the creation of a new Activity API. Following last year’s Atlas Camp announcement from our CTO Sri Viswanath, Atlassian is moving onto GraphQL - new Activity API is one the first pieces of the GraphQL Atlassian Platform and is the technology behind start.atlassian.com.
Join Sergey Meshkov, Senior Developer, who will provide you a sneak peek of the new GraphQL Activity API as it will soon be available to our vendors.
Design Your Next App with the Atlassian Vendor Sketch PluginAtlassian
Our designers work 3x quicker with the Atlassian Vendor Sketch Plugin — and now we’re unleashing these superpowers to the Atlassian Ecosystem. If you mockup screens for code or marketing, we’ll help you drag and drop your way to an Atlaskit design in less than 10 minutes. And if you’re a designer, you’ll want to hear about our pixel-perfect component library and suite of seamless Sketch integrations.
Join Atlassian’s resident Sketch aficionado, Huw Evans, to learn about:
Sketch Components: If it’s in Atlaskit, it’s now in Sketch. And introducing the Symbol Palette, the quickest way to find the right component for the job.
Product Templates: Spark inspiration by building your designs inside realistic screens from Jira & Confluence — or craft hero images for your Marketplace listing!
Color and Text Styles: Heard of N75? H400? If those mean nothing to you, we’ll run through how to make your users feel at home by using Atlassian colors & typography, right inside Sketch.
Data Suppliers: Say goodbye to Lorem Ipsum. Learn how to use Sketch Data Suppliers to generate realistic copy using live data from Jira, Confluence and Bitbucket. Bonus: How we used AI to create people who don’t exist!
♀️ It's All Open Source: How we made it really easy to customise the Atlassian Vendor Sketch Plugin for your team's needs.
Tear Up Your Roadmap and Get Out of the BuildingAtlassian
The document discusses conducting customer research by tearing up existing roadmaps and getting out of the building. It recommends running a research spike with the team to define what needs to be learned. Tips are provided for recruiting participants through support, community, and sales teams. Conducting customer interviews is discussed, including roles for scribes and interviewers. Analyzing interviews by consolidating themes from transcripts is also covered. An example analysis identified themes around customer journeys, collaboration as a team sport, and overwhelming demand for participation. The document encourages being honest about whether a research spike could be run and why or why not.
Nailing Measurement: a Framework for Measuring Metrics that MatterAtlassian
When it comes to designing apps and new features, we just can't get enough of metrics. In an age where we can collect data from almost anything, how can we cut through the noise and focus on the right metrics to measure the success and failures of the apps that we’re building?
Join Atlassian Product Manager Josephine Lee as she delves through what exactly makes a good metric. Throughout the talk, we’ll walk through real Atlassian examples of good and bad metrics. By exploring a framework for measurement, we’ll cover detailed features that showcase how best to measure and choose the right set of success, supportive, and counter metrics.
You'll walk away with tips and learnings from Atlassian’s approach to measuring success, and learn how to use data and metrics to inspire action in your apps.
Building Apps With Color Blind Users in MindAtlassian
Color-blind people are using your apps. 1 in 12 men is color blind. And for women, this is 1 in 200.
Building apps that work well for color blind people is not difficult. Some simple techniques help us with the design of our interface. And some tools help us see what color blind people see.
In this talk, Maarten Arts of Avisi will look at common varieties of color blindness. We will look at apps through the eyes of a color-blind person. And we will discover what color-blind people struggle with.
Regardless of whether you're a designer or developer, this talk will equip you with the skills and the tools you need to make sure that your app works for color-blind people.
Creating Inclusive Experiences: Balancing Personality and Accessibility in UX...Atlassian
The words we choose have the power to include or alienate our users. The reality is that for many, English is spoken as a second language. And unless you're going to localize your product for those major non-English speaking markets, you'll need to thoughtfully create content that is accessible to a larger audience.
But how do we create products that maintain a sense of personality without isolating a wide audience of non-native speakers?
Join Atlassian Content Designer, Roana Bilia, as she walks you through why thoughtful, inclusive content, is key to creating well-designed user experiences. You'll walk away with foundational principles for good UX copy when optimizing your product UI, a few quick wins that you as creators and developers can incorporate into your next products, as well as a set of mistakes to avoid that companies—including Atlassian—have made, which prioritized native speakers but isolated non-native speakers.
Beyond Diversity: A Guide to Building Balanced TeamsAtlassian
We hear it all the time, and we get it. Diversity and inclusion are important! But isn't it an HR problem? HR may be able to help with diversity but inclusion or creating an inclusive environment is everyone's responsibility. So how do we create an inclusive environment that celebrates diversity and engages and supports everyone? Isabel Nyo will be sharing best practices and lessons she has learned along the way. She will also be sharing her experience as a minority, a female technical leader, in the technology industry.
The Road(map) to Las Vegas - The Story of an Emerging Self-Managed TeamAtlassian
In September 2018, K15t took its mission to go self-managed to the next-level when the entire company worked together to decide on the Next Big Thing™ to build for Atlassian users and present it at Summit in Las Vegas.
In this session, Anshuman Dash, an intern turned software engineer, turned product manager, shares his journey of professional self-discovery. In under five months, he joins a freshly assembled, self-managed team in building a new Atlassian Marketplace app.
Dash will give a quick intro to what it means for a team to be self-managed. Then, he'll share his observations and experiences on the team, as well as the best-practices, patterns, and processes K15t has discovered along the way.
Whether you are a new team with a kick-ass product idea or a big company figuring out ways to scale, this talk will provide you with practical tips and ideas your team can try out!
Designing for the enterprise comes with a unique set of challenges; ensuring readability and accessibility at scale, meeting the needs of multi-layered organizations, and building a trust when your software - used by dozens of thousands of employees - is considered mission-critical.
At Atlassian, we've spent countless hours digging deep into our enterprise customer's needs and we've gathered a vast repository of insights.
In this talk, Pawel Wodkowski, a senior designer on Jira Server, will share all that we've learned from our research (while not being shy about busting some of those wild admin myths!). You'll get a crash course in what it means to design for scale the Atlassian way.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Pushing the limits of ePRTC: 100ns holdover for 100 days
5 Thing You're Not Doing, 4 Things You Should Stop Doing & 3 Things You Should Keep Doing in Your Plugin - Atlassian Summit 2010 - Lightning Talks
1. Getting Started with Plugin Development
Matt Ryall
Confluence Technical Lead, Atlassian
Atlassian Summit 2010
1
Monday, June 14, 2010 1
2. Why have you never developed a plugin?
‣ Don’t know how
‣ Not a Java programmer
‣ Too hard
‣ Too much initial set-up
‣ Don’t know the product APIs
2
Monday, June 14, 2010 2
3. Little-Known Fact #1:
Plugins don’t need to be written in Java.
3
Monday, June 14, 2010 3
4. Plugins types that don’t use Java
‣ Web Items – Add custom links to your application
‣ Web Panels – Add additional content on the page
‣ Web Resources – Restyle or customise the page with CSS and JavaScript
‣ External Gadget Providers or Gadget Plugins – Custom Google gadgets
‣ Confluence User Macros – Create simple Confluence macros
4
Monday, June 14, 2010 4
5. Use web technologies instead
‣ HTML
‣ CSS
‣ JavaScript (with jQuery)
5
Monday, June 14, 2010 5
6. Little-Known Fact #2:
Plugins don’t need to be distributed in a JAR file.
6
Monday, June 14, 2010 6
7. Upload plugins directly
‣ If there’s no other files, just upload the XML descriptor file.
‣ This works for:
• Web Items
• Web Panels
• Web Resources (sometimes)
• Confluence User Macros
‣ External Gadget Providers can be installed via URL
7
Monday, June 14, 2010 7
8. XML file template
<atlassian-plugin key="com.example.plugins.sample"
name="My Sample Plugin" plugins-version="2">
<plugin-info>
<version>1.0</version>
<vendor>My Company</vendor>
</plugin-info>
... your stuff goes here ...
</atlassian-plugin>
http://confluence.atlassian.com/display/CONFDEV/Creating+your+Plugin+Descriptor
8
Monday, June 14, 2010 8
9. Little-Known Fact #3:
You don’t need to know Java to create a JAR file.
9
Monday, June 14, 2010 9
10. Use the plugin SDK
‣ First, create the plugin skeleton:
• Run atlas-create-confluence-plugin and it will prompt for values
‣ Delete the src/main/java and src/test directories
‣ Put CSS, JS files in the src/main/resources directory
‣ Build a JAR with your files
• Run atlas-package and it will build a new JAR file in the target/ directory
10
Monday, June 14, 2010 10
11. Plugin structure with no Java code
‣ POM includes instructions for SDK
‣ Plugin content is under src/main/resources/
‣ Run atlas-package and the plugin JAR
appears in target/ directory
11
Monday, June 14, 2010 11
13. Example: Link to your Company Intranet
‣ Adding a link to Confluence’s global Browse
menu
• Also works in other places
• Also works in other Atlassian applications
‣ Done in only 2½ steps
http://confluence.atlassian.com/display/CONFDEV/Web+UI+Module
13
Monday, June 14, 2010 13
14. Step 1: Create a Web Item
<web-item key="company-intranet" name="Company Intranet"
section="system.browse/global" weight="40">
<label>My Company Intranet</label>
<link>http://intranet.example.com/</link>
</web-item>
http://confluence.atlassian.com/display/CONFDEV/Web+UI+Module
14
Monday, June 14, 2010 14
15. Step 2: Drop it in the XML template
<atlassian-plugin key="com.example.plugins.sample"
name="My Sample Plugin" plugins-version="2">
<plugin-info>
<version>1.0</version>
<vendor>My Company</vendor>
</plugin-info>
<web-item key="company-intranet" name="Company Intranet"
section="system.browse/global" weight="40">
<label>My Company Intranet</label>
<link>http://intranet.example.com/</link>
</web-item>
</atlassian-plugin>
15
Monday, June 14, 2010 15
19. Step 1: Create your User Macro
<user-macro key="green" name="green" hasBody="false"
bodyType="raw" outputType="html">
<template><![CDATA[
<span style="background: green; color: white;
padding: 4px 12px">GREEN</span>
]]></template>
</user-macro>
‣ You might also want to create ones for {red} and {yellow}…
http://confluence.atlassian.com/display/CONFDEV/User+Macro+Module
19
Monday, June 14, 2010 19
20. Step 2: Drop it in the XML template
<atlassian-plugin key="com.example.plugins.sample"
name="My Sample Plugin" plugins-version="2">
<plugin-info>
<version>1.0</version>
<vendor>My Company</vendor>
</plugin-info>
<user-macro key="green" name="green" hasBody="false"
bodyType="raw" outputType="html">
<template><![CDATA[
<span style="background: green; color: white;
padding: 4px 12px">GREEN</span>
]]></template>
</user-macro>
</atlassian-plugin>
20
Monday, June 14, 2010 20
23. More examples
Devoxx Conference Twitter Ticker – JavaScript User Macro
23
Monday, June 14, 2010 23
24. More examples
Atlassian’s Staff Directory – just HTML, CSS and JavaScript
24
Monday, June 14, 2010 24
25. Scripting support (alpha stage)
‣ Scripting Extender Plugin – Adds support for scripting languages in your plugin
‣ Groovy Plugins – Lightning talk coming up next…
‣ JavaScript Plugins – At prototype stage, might be bundled soon.
‣ Java 6 Scripting Engine – Can use this with some Java code.
‣ Area of interest for some Atlassian developers – 20% projects and labs
work ongoing.
25
Monday, June 14, 2010 25