Java Bytecode: Passing Parameters
Download as pptx, pdf2 likes8,640 views
The document shows the bytecode for a method that increments an integer value. It loads the this object onto the stack, invokes a method to initialize a local variable, then invokes a private incValue method, passing the local variable. IncValue loads the integer, increments it by 1, and returns an Integer object.
1 of 15
Downloaded 90 times
Ad
Recommended
Programming JVM Bytecode with Jitescript
Programming JVM Bytecode with JitescriptJoe Kutner The document discusses Java Virtual Machine (JVM) bytecode, detailing the structure, compilation process, and examples of Java classes. It includes instructions on reading bytecode, diagnosing performance issues, and offers tools for reverse engineering and debugging. Additionally, it mentions various JVM opcodes and their significance in method invocation and operand stack manipulation.
Mirage For Beginners
Mirage For BeginnersWilson Su This document introduces Mirage, an API mocking library that allows front-end developers to simulate API responses before the backend is ready. It provides code examples for setting up a Mirage server, creating routes, and handling requests with mock data in an in-memory database. Additionally, it outlines project folder structure and configuration settings for efficient use and organization of mock API routes.
Registro de venta
Registro de ventalupe ga The document describes a Java class called frmregistroventa that contains a GUI for registering employee data. It initializes components like text fields, radio buttons, and buttons for actions like adding, showing, searching, and modifying employee records stored in a ListaRegistro list. The class contains methods that will be called when the different buttons are clicked to perform the corresponding actions on the employee data.
Testing your javascript code with jasmine
Testing your javascript code with jasmineRubyc Slides This document discusses using Jasmine to test JavaScript code. It describes Jasmine as a behavior driven development framework for JavaScript testing. It then provides instructions on installing Jasmine, creating spec files to contain test cases, and including source code files. The document uses an example of testing a master-slave checkbox relationship to demonstrate how to set up tests, DOM elements, and code the tests against the actual code implementation.
Programming JVM Bytecode
Programming JVM BytecodeJoe Kutner The document provides a detailed analysis of Java Virtual Machine (JVM) bytecode generated from a simple Java program that creates an ArrayList and adds a string to it. It includes various javap outputs that display the compiled methods, class structure, and internal pool references, along with breakdowns of method invocations and stack operations. The information also touches on different operational instructions and the memory structure utilized by the JVM during execution.
Jasmine BDD for Javascript
Jasmine BDD for JavascriptLuis Alfredo Porras Páez Jasmine is a BDD framework for testing JavaScript code. It does not depend on other frameworks and does not require a DOM. Jasmine uses specs, expectations, suites, and matchers to define tests and make assertions. It also supports features for testing asynchronous code and spying on functions. Jasmine provides tools like spies, stubs, fakes, and mocks to help test code behavior.
Jasmine - why JS tests don't smell fishy
Jasmine - why JS tests don't smell fishyIgor Napierala Unit testing JavaScript code with Jasmine allows developers to test functionality in isolation through matchers, spies, and asynchronous handling. Key benefits include cheaper QA, better documentation, improved code quality, and easier debugging. While some are deterred by complex asynchronous code or small projects, unit testing pays off through early bug detection and confidence that features work as intended.
JavaScript Unit Testing with Jasmine
JavaScript Unit Testing with JasmineRaimonds Simanovskis This document discusses JavaScript unit testing with Jasmine. It provides an overview of Jasmine's syntax including describes, contexts, matches, spies and stubs. It also discusses tools that can be used with Jasmine like jasmine-jquery for DOM testing and jasmine-given for behavior-driven development style tests.
Workshop 5: JavaScript testing
Workshop 5: JavaScript testingVisual Engineering The document provides an in-depth overview of JavaScript testing emphasizing the importance of automated testing over manual testing due to its efficiency and reliability. It covers concepts such as test-driven development (TDD), various testing frameworks including Jasmine and Sinon, and illustrates the use of spies, asynchronous testing, and the Karma test runner. Additionally, it addresses common issues and best practices in unit testing while referencing further resources for more comprehensive learning.
Javascript Testing with Jasmine 101
Javascript Testing with Jasmine 101Roy Yu The document discusses the importance of unit testing in software development, emphasizing its role in reducing bugs, improving software design, and facilitating communication among team members. It introduces Jasmine, a behavior-driven testing framework for JavaScript, outlining basic testing concepts such as suites, specs, matchers, and spies, including examples for clarity. Furthermore, it highlights best practices in test-driven and behavior-driven development, advocating for clear specifications that enhance understanding between technical and non-technical stakeholders.
Dependency Injection with CDI in 15 minutes
Dependency Injection with CDI in 15 minutesAntonio Goncalves This document discusses dependency injection in CDI. It begins with a brief history of CDI and then covers the different ways that dependencies can be injected including via attributes, constructors, setters, qualifiers and programmatic lookup. It also discusses how to inject producers like entity managers and how CDI enables loose coupling and strong typing. The document concludes by emphasizing that CDI is capable of much more than just dependency injection.
Building Maintainable Applications in Apex
Building Maintainable Applications in ApexJeffrey Kemp The document is the agenda for a talk on building maintainable applications in Apex. It discusses maintainable PL/SQL and using an MVC architecture. It also provides examples of unclear and clear code and emphasizes consistency, readability, and writing code that future maintainers will appreciate. The document includes controversial statements, quotes, and code examples to illustrate techniques for writing maintainable code.
Thoughts On Learning A New Programming Language
Thoughts On Learning A New Programming LanguagePatricia Aas The document discusses strategies for learning programming languages, particularly C#, emphasizing the importance of understanding basic syntax, identifying cognates and false cognates between languages, and recognizing the evolution of programming concepts. It provides examples of code snippets and highlights differences in terminology and functionality across languages like C++, Java, and Python. The content also reflects on teaching methods and encourages leveraging known terms to facilitate learning for students.
Voxxed Days Vilnius 2015 - Having fun with Javassist
Voxxed Days Vilnius 2015 - Having fun with JavassistAnton Arhipov The document discusses using Javassist, a Java bytecode engineering library, to dynamically generate Java proxies at runtime. It provides examples of using Javassist with a Java agent to transform class files and generate proxies within a ClassFileTransformer. It also summarizes how Javassist is used within the JRebel application reload agent to refresh configurations and notify plugins of class reloading.
Stop Making Excuses and Start Testing Your JavaScript
Stop Making Excuses and Start Testing Your JavaScriptRyan Anklam The document provides tips for adding testing to JavaScript projects. It recommends choosing a testing environment and dialect, then setting up the tests by installing dependencies and configuring files. Common issues like testing asynchronous code and methods that call other methods can be addressed with spies, stubs, mocks and promises. Tests should focus on isolated units of code and avoid direct DOM manipulation when possible. Automating testing through build tools like Grunt and Testem helps to easily run and watch tests. Overall, the document emphasizes making testing easy by writing maintainable, modular code and setting up automation.
Celery
CeleryÒscar Vilaplana This document discusses using Celery and RabbitMQ to implement asynchronous task queues. It provides an overview of Celery and RabbitMQ, how to set them up, configure tasks, schedule and retry tasks, and examples of using task queues for importing large files and sending complex emails. The key benefits highlighted are decoupling tasks from the main system, scalability, and ability to distribute tasks across multiple workers.
Side effects-con-redux
Side effects-con-reduxNicolas Quiceno Benavides The document discusses using Redux middleware like redux-thunk and redux-saga to handle asynchronous actions and side effects in Redux applications. Redux-thunk allows returning functions from action creators to support asynchronous logic. Redux-saga uses generator functions to declaratively define asynchronous flows using effects. It provides capabilities like parallelism, cancellation, and composition that are more complex with redux-thunk. Both libraries make it easier to handle asynchronous logic while avoiding complex race conditions and keeping side effects separate from the reducer logic.
Zen: Building Maintainable Catalyst Applications
Zen: Building Maintainable Catalyst ApplicationsJay Shirley The document discusses best practices for application maintenance, emphasizing the importance of error handling, better logging, and proper configuration management. It advocates for the use of Moose and emphasizes the need for effective testing and deployment strategies. Additionally, it suggests ways to manage dependencies and user environments to ensure smooth application performance.
Testing Against AWS APIs Go
Testing Against AWS APIs GoStephen Scaffidi The document discusses testing AWS APIs using Go, focusing on creating mock implementations for EC2 API interactions. It provides sample code for establishing AWS sessions, retrieving instance IDs, and testing the functionality using assertions. The author emphasizes the challenges of testing live systems and the importance of using mocks for efficient testing.
Rails is not just Ruby
Rails is not just RubyMarco Otte-Witte The document discusses best practices for integrating JavaScript with Ruby on Rails, emphasizing the importance of clean and maintainable code. It compares traditional methods, such as remote helpers, with modern approaches like full separation and explicit controls for managing JavaScript behaviors. The author advocates for avoiding classic solutions and suggests utilizing resources for further learning and improvement in coding standards.
The Anatomy of an Exploit (CPPP 2019)
The Anatomy of an Exploit (CPPP 2019)Patricia Aas The document discusses the process of exploit development, particularly in C and C++. It illustrates various vulnerabilities through code snippets, focusing on buffer overflows and unsafe functions, and outlines how to exploit these weaknesses. Additionally, it highlights the advantages of using C++ over C for security and includes examples of automating exploits and fixing vulnerabilities.
Testing Javascript with Jasmine
Testing Javascript with JasmineTim Tyrrell The document discusses the importance of unit testing JavaScript, particularly using the Jasmine framework, comparing it with RSpec in syntax and functionality. It details the setup and usage of Jasmine with various JavaScript libraries and frameworks, including jQuery and Ruby on Rails, emphasizing the ease of integration and testing. Additionally, it highlights the significance of testing tools such as CoffeeScript and offers resources for further exploration on this topic.
First glance at Akka 2.0
First glance at Akka 2.0Vasil Remeniuk Akka 2.0 allows actors to be distributed across multiple nodes in a cluster in a transparent manner. It introduces new concepts like actor addresses and deployment configurations. The clustering functionality leverages ZooKeeper for distributed coordination and stores serialized actor factories. This allows actors to be dynamically created, migrated, and replicated across nodes for fault tolerance and load balancing. Composable futures also allow combining results from multiple asynchronous messages.
Introduction to CDI and DI in Java EE 6
Introduction to CDI and DI in Java EE 6Ray Ploski The document discusses concepts related to productive, simple, and modern application development. It introduces the concepts of dependency injection and contextual conversations in CDI, including scopes, qualifiers, stereotypes, events, and extensions. It also discusses integrating Spring components into CDI and the goals of the Seam 3 Spring module.
Excellent
ExcellentMarco Otte-Witte The document introduces Excellent, a static code analysis tool for Ruby on Rails that provides insights into potential issues rather than simply identifying errors. It includes various complexity measures and Rails-specific checks to enhance code quality. Users can execute analyses via Rake and generate HTML reports for further review.
Reactive programming with RxJS - ByteConf 2018
Reactive programming with RxJS - ByteConf 2018Tracy Lee The document discusses various programming concepts and functionalities related to JavaScript and React, particularly focusing on handling asynchronous data streams using RxJS. It covers practical applications of observables and subjects in managing user interactions and socket connections. Additionally, it includes examples for data filtering, mapping, and state management in a React application.
The Anatomy of an Exploit (NDC TechTown 2019)
The Anatomy of an Exploit (NDC TechTown 2019)Patricia Aas This document provides an overview of an exploit development process. It begins by discussing how exploits program the "weird machine" of vulnerable programs through memory manipulation. It then walks through developing a stack buffer overflow exploit against a vulnerable C program. Various compiler protections like stack canaries and ASLR are bypassed. The document generates a pattern to find the offset and writes an exploit program to automate writing an exploit string to trigger the vulnerability and redirect execution.
RSpec
RSpecMarco Otte-Witte The document discusses RSpec, a behavior-driven development (BDD) framework for testing Ruby code. It describes how RSpec allows writing tests in a natural language style using "should" statements. Examples are provided for different types of RSpec tests, including model, controller, and view tests. Shared examples, custom matchers, and integration with Cucumber for writing tests in a storytelling format are also covered. The document concludes with information on installing and running RSpec and generating reports from test results.
JavaZone 2022 - Building Kotlin DSL.pdf
JavaZone 2022 - Building Kotlin DSL.pdfAnton Arhipov The document discusses Kotlin DSL and provides examples of using Kotlin as a domain specific language. It demonstrates how to build type-safe builders using Kotlin, including defining DSL blocks, extension functions and properties, infix notation, lambda receivers, and context receivers to define internal and external DSLs. Code samples are provided of building clients and dates using DSL syntax and context requirements.
Idiomatic kotlin
Idiomatic kotlinAnton Arhipov The document discusses idiomatic Kotlin programming. It covers several topics including:
- Using expressions idiomatically in Kotlin like if/when expressions
- Examples of idiomatic patterns from the Kotlin standard library
- Best practices for null safety using safe calls, let, elvis operator
- Idiomatic use of classes, functions, and data classes
- Leveraging the Kotlin standard library
More Related Content
What's hot (20)
Workshop 5: JavaScript testing
Workshop 5: JavaScript testingVisual Engineering The document provides an in-depth overview of JavaScript testing emphasizing the importance of automated testing over manual testing due to its efficiency and reliability. It covers concepts such as test-driven development (TDD), various testing frameworks including Jasmine and Sinon, and illustrates the use of spies, asynchronous testing, and the Karma test runner. Additionally, it addresses common issues and best practices in unit testing while referencing further resources for more comprehensive learning.
Javascript Testing with Jasmine 101
Javascript Testing with Jasmine 101Roy Yu The document discusses the importance of unit testing in software development, emphasizing its role in reducing bugs, improving software design, and facilitating communication among team members. It introduces Jasmine, a behavior-driven testing framework for JavaScript, outlining basic testing concepts such as suites, specs, matchers, and spies, including examples for clarity. Furthermore, it highlights best practices in test-driven and behavior-driven development, advocating for clear specifications that enhance understanding between technical and non-technical stakeholders.
Dependency Injection with CDI in 15 minutes
Dependency Injection with CDI in 15 minutesAntonio Goncalves This document discusses dependency injection in CDI. It begins with a brief history of CDI and then covers the different ways that dependencies can be injected including via attributes, constructors, setters, qualifiers and programmatic lookup. It also discusses how to inject producers like entity managers and how CDI enables loose coupling and strong typing. The document concludes by emphasizing that CDI is capable of much more than just dependency injection.
Building Maintainable Applications in Apex
Building Maintainable Applications in ApexJeffrey Kemp The document is the agenda for a talk on building maintainable applications in Apex. It discusses maintainable PL/SQL and using an MVC architecture. It also provides examples of unclear and clear code and emphasizes consistency, readability, and writing code that future maintainers will appreciate. The document includes controversial statements, quotes, and code examples to illustrate techniques for writing maintainable code.
Thoughts On Learning A New Programming Language
Thoughts On Learning A New Programming LanguagePatricia Aas The document discusses strategies for learning programming languages, particularly C#, emphasizing the importance of understanding basic syntax, identifying cognates and false cognates between languages, and recognizing the evolution of programming concepts. It provides examples of code snippets and highlights differences in terminology and functionality across languages like C++, Java, and Python. The content also reflects on teaching methods and encourages leveraging known terms to facilitate learning for students.
Voxxed Days Vilnius 2015 - Having fun with Javassist
Voxxed Days Vilnius 2015 - Having fun with JavassistAnton Arhipov The document discusses using Javassist, a Java bytecode engineering library, to dynamically generate Java proxies at runtime. It provides examples of using Javassist with a Java agent to transform class files and generate proxies within a ClassFileTransformer. It also summarizes how Javassist is used within the JRebel application reload agent to refresh configurations and notify plugins of class reloading.
Stop Making Excuses and Start Testing Your JavaScript
Stop Making Excuses and Start Testing Your JavaScriptRyan Anklam The document provides tips for adding testing to JavaScript projects. It recommends choosing a testing environment and dialect, then setting up the tests by installing dependencies and configuring files. Common issues like testing asynchronous code and methods that call other methods can be addressed with spies, stubs, mocks and promises. Tests should focus on isolated units of code and avoid direct DOM manipulation when possible. Automating testing through build tools like Grunt and Testem helps to easily run and watch tests. Overall, the document emphasizes making testing easy by writing maintainable, modular code and setting up automation.
Celery
CeleryÒscar Vilaplana This document discusses using Celery and RabbitMQ to implement asynchronous task queues. It provides an overview of Celery and RabbitMQ, how to set them up, configure tasks, schedule and retry tasks, and examples of using task queues for importing large files and sending complex emails. The key benefits highlighted are decoupling tasks from the main system, scalability, and ability to distribute tasks across multiple workers.
Side effects-con-redux
Side effects-con-reduxNicolas Quiceno Benavides The document discusses using Redux middleware like redux-thunk and redux-saga to handle asynchronous actions and side effects in Redux applications. Redux-thunk allows returning functions from action creators to support asynchronous logic. Redux-saga uses generator functions to declaratively define asynchronous flows using effects. It provides capabilities like parallelism, cancellation, and composition that are more complex with redux-thunk. Both libraries make it easier to handle asynchronous logic while avoiding complex race conditions and keeping side effects separate from the reducer logic.
Zen: Building Maintainable Catalyst Applications
Zen: Building Maintainable Catalyst ApplicationsJay Shirley The document discusses best practices for application maintenance, emphasizing the importance of error handling, better logging, and proper configuration management. It advocates for the use of Moose and emphasizes the need for effective testing and deployment strategies. Additionally, it suggests ways to manage dependencies and user environments to ensure smooth application performance.
Testing Against AWS APIs Go
Testing Against AWS APIs GoStephen Scaffidi The document discusses testing AWS APIs using Go, focusing on creating mock implementations for EC2 API interactions. It provides sample code for establishing AWS sessions, retrieving instance IDs, and testing the functionality using assertions. The author emphasizes the challenges of testing live systems and the importance of using mocks for efficient testing.
Rails is not just Ruby
Rails is not just RubyMarco Otte-Witte The document discusses best practices for integrating JavaScript with Ruby on Rails, emphasizing the importance of clean and maintainable code. It compares traditional methods, such as remote helpers, with modern approaches like full separation and explicit controls for managing JavaScript behaviors. The author advocates for avoiding classic solutions and suggests utilizing resources for further learning and improvement in coding standards.
The Anatomy of an Exploit (CPPP 2019)
The Anatomy of an Exploit (CPPP 2019)Patricia Aas The document discusses the process of exploit development, particularly in C and C++. It illustrates various vulnerabilities through code snippets, focusing on buffer overflows and unsafe functions, and outlines how to exploit these weaknesses. Additionally, it highlights the advantages of using C++ over C for security and includes examples of automating exploits and fixing vulnerabilities.
Testing Javascript with Jasmine
Testing Javascript with JasmineTim Tyrrell The document discusses the importance of unit testing JavaScript, particularly using the Jasmine framework, comparing it with RSpec in syntax and functionality. It details the setup and usage of Jasmine with various JavaScript libraries and frameworks, including jQuery and Ruby on Rails, emphasizing the ease of integration and testing. Additionally, it highlights the significance of testing tools such as CoffeeScript and offers resources for further exploration on this topic.
First glance at Akka 2.0
First glance at Akka 2.0Vasil Remeniuk Akka 2.0 allows actors to be distributed across multiple nodes in a cluster in a transparent manner. It introduces new concepts like actor addresses and deployment configurations. The clustering functionality leverages ZooKeeper for distributed coordination and stores serialized actor factories. This allows actors to be dynamically created, migrated, and replicated across nodes for fault tolerance and load balancing. Composable futures also allow combining results from multiple asynchronous messages.
Introduction to CDI and DI in Java EE 6
Introduction to CDI and DI in Java EE 6Ray Ploski The document discusses concepts related to productive, simple, and modern application development. It introduces the concepts of dependency injection and contextual conversations in CDI, including scopes, qualifiers, stereotypes, events, and extensions. It also discusses integrating Spring components into CDI and the goals of the Seam 3 Spring module.
Excellent
ExcellentMarco Otte-Witte The document introduces Excellent, a static code analysis tool for Ruby on Rails that provides insights into potential issues rather than simply identifying errors. It includes various complexity measures and Rails-specific checks to enhance code quality. Users can execute analyses via Rake and generate HTML reports for further review.
Reactive programming with RxJS - ByteConf 2018
Reactive programming with RxJS - ByteConf 2018Tracy Lee The document discusses various programming concepts and functionalities related to JavaScript and React, particularly focusing on handling asynchronous data streams using RxJS. It covers practical applications of observables and subjects in managing user interactions and socket connections. Additionally, it includes examples for data filtering, mapping, and state management in a React application.
The Anatomy of an Exploit (NDC TechTown 2019)
The Anatomy of an Exploit (NDC TechTown 2019)Patricia Aas This document provides an overview of an exploit development process. It begins by discussing how exploits program the "weird machine" of vulnerable programs through memory manipulation. It then walks through developing a stack buffer overflow exploit against a vulnerable C program. Various compiler protections like stack canaries and ASLR are bypassed. The document generates a pattern to find the offset and writes an exploit program to automate writing an exploit string to trigger the vulnerability and redirect execution.
RSpec
RSpecMarco Otte-Witte The document discusses RSpec, a behavior-driven development (BDD) framework for testing Ruby code. It describes how RSpec allows writing tests in a natural language style using "should" statements. Examples are provided for different types of RSpec tests, including model, controller, and view tests. Shared examples, custom matchers, and integration with Cucumber for writing tests in a storytelling format are also covered. The document concludes with information on installing and running RSpec and generating reports from test results.
More from Anton Arhipov (20)
JavaZone 2022 - Building Kotlin DSL.pdf
JavaZone 2022 - Building Kotlin DSL.pdfAnton Arhipov The document discusses Kotlin DSL and provides examples of using Kotlin as a domain specific language. It demonstrates how to build type-safe builders using Kotlin, including defining DSL blocks, extension functions and properties, infix notation, lambda receivers, and context receivers to define internal and external DSLs. Code samples are provided of building clients and dates using DSL syntax and context requirements.
Idiomatic kotlin
Idiomatic kotlinAnton Arhipov The document discusses idiomatic Kotlin programming. It covers several topics including:
- Using expressions idiomatically in Kotlin like if/when expressions
- Examples of idiomatic patterns from the Kotlin standard library
- Best practices for null safety using safe calls, let, elvis operator
- Idiomatic use of classes, functions, and data classes
- Leveraging the Kotlin standard library
TechTrain 2019 - (Не)адекватное техническое интервью
TechTrain 2019 - (Не)адекватное техническое интервьюAnton Arhipov Документ обсуждает проблемы технических собеседований в IT, подчеркивая недостатки подхода к оценке кандидатов на основе алгоритмических задач. Упоминается, что для успешной интеграции новых инженеров в проект требуется гораздо больше времени, чем некоторые работодатели предполагают. Также рассматриваются примеры типичных вопросов на собеседованиях и различия между знаниями языков программирования и реальной практикой.
Build pipelines with TeamCity
Build pipelines with TeamCityAnton Arhipov The document outlines the capabilities of TeamCity by JetBrains, detailing its ability to manage over 2700 projects and 16,000 build configurations. It emphasizes the need for build pipelines to optimize processes like source checkout, compilation, testing, and reporting, while also discussing dependency management and queue optimization. Additionally, it highlights the time-saving benefits of using TeamCity for building and testing software projects.
Build pipelines with TeamCity
Build pipelines with TeamCityAnton Arhipov TeamCity is a build management and continuous integration tool created by JetBrains that allows building pipelines of steps. It supports over 2000 projects with 12,000 build configurations running on 500 agents. Key features include a Kotlin DSL, HA read-only servers, Docker runner improvements, templates for step ordering, enforced settings, .NET Core support, and plugins. Pipelines allow breaking up builds into sequential steps like compiling, running tests, and publishing results to improve efficiency.
Devoxx Ukraine 2018 - Kotlin DSL in under an hour
Devoxx Ukraine 2018 - Kotlin DSL in under an hourAnton Arhipov The document discusses the use of Kotlin DSL for building domain-specific applications with various examples, including HTML creation and UI elements like forms and buttons. It also covers integration with Gradle for project management and demonstrates type-safe builders for object construction. Additionally, it explores features like extension properties and methods, and provides links to relevant GitHub repositories for further exploration.
GeeCON Prague 2018 - Kotlin DSL in under an hour
GeeCON Prague 2018 - Kotlin DSL in under an hourAnton Arhipov This document discusses Kotlin DSL, showcasing various examples and tools related to it, including integration with frameworks like Ktor and Anko. It covers building blocks, type-safe builders, and utilizing Gradle with Kotlin DSL, along with some specific code snippets for contexts like web development and database transactions. Additionally, it highlights resources and repositories for further exploration of Kotlin DSL capabilities.
Build pipelines with TeamCity and Kotlin DSL
Build pipelines with TeamCity and Kotlin DSLAnton Arhipov - TeamCity allows building software projects and managing build pipelines for continuous integration and delivery (CI/CD)
- A build pipeline in TeamCity refers to the sequence of build steps such as compiling code, running tests, and deploying artifacts that are automatically triggered by code changes
- The document demonstrates how to define a build pipeline in TeamCity using Kotlin DSL that compiles and packages a Java application project and its dependency library project
Build pipelines with TeamCity
Build pipelines with TeamCityAnton Arhipov A build pipeline refers to the automated process of building software by breaking it down into discrete steps. This document discusses how TeamCity, a build management and continuous integration tool, can be used to create build pipelines. It provides an example pipeline with steps for checking out sources, compiling code, running tests at different stages, generating reports, and publishing results. The benefits of a pipeline include running different test types in parallel and tracking dependencies between steps to speed up the overall build process.
JavaDay Kiev 2017 - Integration testing with TestContainers
JavaDay Kiev 2017 - Integration testing with TestContainersAnton Arhipov This document introduces TestContainers, an open source Java library that supports integration testing for applications that depend on external resources like databases. It allows tests to use real Docker containers to manage these dependent services. Tests run quickly and are portable across environments because the containers are started and stopped for each test. The document provides examples of using TestContainers with Spring Boot tests to launch containers for PostgreSQL and Redis, and to configure a MockServer container to handle external API dependencies. It suggests TestContainers is useful for testing microservices and Java agents that depend on external services or APIs.
GeeCON Prague 2017 - TestContainers
GeeCON Prague 2017 - TestContainersAnton Arhipov The document discusses the importance of integration testing and introduces Testcontainers as a solution for creating reproducible testing environments using Docker. It presents examples of integrating Testcontainers with Java applications, particularly with Spring Boot, and illustrates how to set up containers for databases like Redis and PostgreSQL. Additionally, it covers the use of MockServer for handling external dependencies in tests.
JavaOne 2017 - The hitchhiker’s guide to Java class reloading
JavaOne 2017 - The hitchhiker’s guide to Java class reloadingAnton Arhipov This document discusses different techniques for reloading Java classes at runtime:
- HotSwap allows reloading individual statements but is limited. Class loaders allow reloading entire classes but each class loader isolates its classes.
- More advanced techniques like Java agents and bytecode instrumentation allow redefining classes in-place and reloading methods, fields, and class hierarchies in a binary-compatible way.
- Demonstrations show reloading an entire "region" of related classes like a service class and its dependencies, allowing a live application thread to see the changes immediately without restarts. Java agents in particular provide a powerful but complex way to implement class reloading.
JavaOne 2017 - TestContainers: integration testing without the hassle
JavaOne 2017 - TestContainers: integration testing without the hassleAnton Arhipov This document introduces TestContainers, an open source tool for running Docker containers as part of integration tests. It discusses why integration testing is important for reproducibility, isolation, and realism. TestContainers allows setting up Docker containers programmatically and automatically cleaning them up after tests complete. It supports starting individual containers, Docker Compose environments, and custom container types. Examples are given for testing services that depend on databases, caches, and external APIs using TestContainers without complex test environment configuration. The document also describes how to use TestContainers to test Java agents by modifying bytecode at runtime within a container during tests.
JavaOne 2017 - The hitchhiker’s guide to Java class reloading
JavaOne 2017 - The hitchhiker’s guide to Java class reloadingAnton Arhipov The document discusses Java class reloading, emphasizing the time lost during container startup and application deployment. It explores technical solutions such as hotswap, class loaders, and JVM features, along with insights from past works on dynamic code evolution. The content also highlights the challenges and complexities associated with implementing these techniques effectively.
JavaZone 2017 - The Hitchhiker’s guide to Java class reloading
JavaZone 2017 - The Hitchhiker’s guide to Java class reloadingAnton Arhipov This document discusses techniques for reloading Java classes at runtime, including using class loaders to load updated classes, Java agents to instrument classes, and frameworks like HotSwap that utilize these techniques. It provides examples of how class loaders can be used to reload specific parts of an application while a program is running. The goal is to achieve hot reloading that is binary compatible and allows updating code without restarting the Java virtual machine.
Riga DevDays 2017 - The hitchhiker’s guide to Java class reloading
Riga DevDays 2017 - The hitchhiker’s guide to Java class reloadingAnton Arhipov This document discusses techniques for reloading Java classes at runtime, known as hot reloading or hot swapping. It begins with an introduction and overview of class loaders, Java agents, and instrumentation which can be used to dynamically modify classes. Specific techniques are then presented for reloading classes, fields, methods and code using custom class loaders and bytecode manipulation. The goal is to allow reloading parts of an application without restarting the Java Virtual Machine.
GeeCON 2017 - TestContainers. Integration testing without the hassle
GeeCON 2017 - TestContainers. Integration testing without the hassleAnton Arhipov The document discusses how to use Testcontainers for integration testing in a Java environment, emphasizing the need for a reproducible and isolated environment for effective testing. It provides examples of setting up containers for various databases and services, and demonstrates using Docker with Spring Boot to facilitate testing of microservices. The document also touches on the use of Java agents for testing different versions and manipulating application behavior at runtime.
JEEConf 2017 - The hitchhiker’s guide to Java class reloading
JEEConf 2017 - The hitchhiker’s guide to Java class reloadingAnton Arhipov The document discusses advanced techniques for class reloading in Java, focusing on hotswap, dynamic code evolution, and safe class evolution in long-lived applications. It references various studies and technical reports that delve into the challenges and methodologies associated with real-time code changes and dynamic class loaders. Additionally, it highlights practical examples and dependencies, such as the Spring Boot DevTools and Java agents for modifying class behavior at runtime.
JEEConf 2017 - Having fun with Javassist
JEEConf 2017 - Having fun with JavassistAnton Arhipov The document discusses the use of Javassist for bytecode manipulation in Java applications, focusing on proxy generation and aspect-oriented programming. It includes examples of class generation, method interception, and the implementation of logging and tracing features. The content also touches on using Java agents for class transformation during runtime.
Ad
Java Bytecode: Passing Parameters
- 1. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3;10: areturnStackvarvalue1valuedepth21323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn51623
- 2. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; 10: areturnStackvarvalue1valuedepth21this323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn51623
- 3. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; 10: areturnStackvarvalue1valuedepth21objectref323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn51623
- 4. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; 10: areturnStackvarvalueobjectref1valuedepth21323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn51623
- 5. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; 10: areturnStackvarvalueobjectref1valuedepth21this323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn51623
- 6. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; 10: areturnStackvarvalueobjectref1valuedepth21objectref32this3private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn51623
- 7. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3;//incValue10: areturnStackvarvalueobjectref1valuedepth21323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn5objectref1623
- 8. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; //incValue10: areturnStackvarvalueobjectref1valuedepth21objectref323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8;4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn5objectref1623
- 9. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; //incValue10: areturnStackvarvalueobjectref1valuedepth21X323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8;// Integer.intValue:()4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn5objectref1623
- 10. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; //incValue10: areturnStackvarvalueobjectref1valuedepth21132X3private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7; 9: areturn5objectref1623
- 11. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; //incValue10: areturnStackvarvalueobjectref1valuedepth21X + 1323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd6: invokestatic #7; 9: areturn5objectref1623
- 12. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; //incValue10: areturnStackvarvalueobjectref1valuedepth21objectref323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7;//Integer.valueOf9: areturn5objectref1623
- 13. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; //incValue10: areturnStackvarvalueobjectref1valuedepth21objectref323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7;9: areturn5objectref1623
- 14. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; 10: areturnStackvarvalueobjectref1valuedepth21objectref323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7;9: areturn51623
- 15. Local Variablespublic java.lang.Object execute(); 0: aload_0 1: invokespecial #2; 4: astore_1 5: aload_0 6: aload_1 7: invokespecial #3; 10: areturnStackvarvalue1valuedepth21objectref323private java.lang.Integer incValue(java.lang.Integer);4varvalue0: aload_1 1: invokevirtual #8; 4: iconst_1 5: iadd 6: invokestatic #7;9: areturn51623