Топ-30 вопросов для собеседования по Struts с ответами (Издание 2026)

Готовитесь к собеседованию по Struts? Будь то поддержка legacy Struts 1 приложений или работа с Struts 2, это руководство охватывает 30 ключевых технических вопросов — архитектура, конфигурация, валидация, миграция и advanced patterns — плюс 10 behavioral/scenario вопросов с стратегическими модельными ответами.

👉 Бесплатная загрузка PDF: Вопросы и ответы для собеседования по Struts

Core Framework Knowledge

1. Struts Architecture & Lifecycle

Struts реализует MVC: ActionServlet (controller) перехватывает запросы, консультируется с struts-config.xml, делегирует в Action class (model interaction), который возвращает ActionForward к JSP (view).

Step	Description
1	Client request → ActionServlet
2	Servlet reads config, locates Action
3	Action executes business logic
4	Returns ActionForward
5	JSP renders response

Пример: E-commerce checkout: Action validates cart, calls payment service, forwards to success/error JSP.

2. Action Class Types (Struts 1)

Type	Characteristics	Use Case
Action	Basic request handling	Simple flows
DispatchAction	Maps multiple methods via param	CRUD on single page
LookupDispatchAction	Key-method map (i18n friendly)	Multi-language UIs
MappingDispatchAction	Uses action mapping for routing	Complex routing

Пример: DispatchAction handles add/edit/delete в одном классе.

3. Struts 1 vs Struts 2: Migration Trade-offs

Aspect	Struts 1	Struts 2
Action Classes	Extend framework base	Plain POJOs
Data Binding	ActionForm beans	Direct POJO via OGNL
Extensibility	Limited	Interceptor-based, highly customizable
Migration Impact	None	Significant refactoring

Upgrade gains: less boilerplate, modern features. Cost: config changes, deprecated components.

4. Struts Configuration System

struts-config.xml (Struts 1) или struts.xml (Struts 2) определяет: form-beans, action-mappings, global-forwards, plug-ins, message-resources. Struts 2 поддерживает модульные struts.xml per package и annotations.

5. Struts 2 Interceptors: Lifecycle & Role

Модульные pre/post-processing единицы (validation, logging, auth, params). Stack выполняется перед Action, затем после в обратном порядке. params interceptor заполняет properties; validation обеспечивает корректность. Уменьшает boilerplate, консистентная cross-cutting logic.

6. Validation Approaches

Type	Advantages	Disadvantages
Declarative (validation.xml)	Centralized, reusable, maintainable	Less flexible for dynamic rules
Programmatic (Action/Form)	Highly customizable	Increases class complexity

Пример: Declarative для email format; programmatic для unique username via DB check.

7. ActionForm vs POJO Forms (Struts 2)

Struts 1: отдельный ActionForm дублирует domain model. Struts 2: прямой POJO binding через OGNL — чище, меньше redundancy, легче testing.

// Struts 1: UserForm extends ActionForm
// Struts 2: User POJO used directly

8. Struts 2 Result Types

Result Type	Purpose
dispatcher	Forward to JSP (default)
redirect	New request cycle (prevents resubmit)
redirectAction	Redirect to another action
chain	Invoke another action directly
stream	Binary output (files, reports)

9. ActionServlet / FilterDispatcher Role

Central controller: интерпретирует config, selects Action, manages lifecycle, invokes logic, determines view. Без него нет predictable routing или MVC enforcement.

10. Internationalization (i18n)

Property files как message resources; auto-selected by locale. Tags: <bean:message> (Struts 1), <s:text> (Struts 2). Features: structured resources, auto locale detection, reusable keys.

Пример: "Username" → "Nombre de usuario" via locale switch.

11. Exception Handling

Declarative: <exception> в config maps exception types to result pages. Programmatic: try-catch в Action. Declarative = consistency; programmatic = contextual responses (auth errors → warning page, system errors → maintenance page).

12. Struts Tag Libraries

Struts 1: <html:form>, <bean:write>, <logic:iterate>. Struts 2: <s:form>, <s:textfield>, <s:iterator>. Bind form fields directly: <html:text property="username"/>.

13. OGNL in Struts 2

Object-Graph Navigation Language: expression evaluation, request-param-to-POJO binding, deep graph navigation. address.street, address.city auto-populate nested objects.

14. RequestProcessor (Struts 1) vs Interceptor Stack (Struts 2)

Feature	RequestProcessor	Interceptor Stack
Extensibility	Limited (subclassing)	Highly flexible (configurable)
Behavior	Monolithic	Modular, distributed
Benefits	Simplicity	Separation of concerns

15. File Upload Implementation

Struts 1: Apache Commons FileUpload. Struts 2: built-in <s:file> tag. Considerations: size limits, MIME validation, secure storage, malicious upload prevention.

16. Struts 2 Flexibility Features

Interceptor architecture, POJO actions, DI support (Spring plugin), custom result types, plugins (JSON, REST, Spring). Example: global auth/logging interceptors eliminate duplication.

17. Struts vs Spring MVC

Aspect	Struts	Spring MVC
Controller	Action-based	Annotation-based
Config	XML-heavy	Lightweight
Testing	Moderate	Very easy
Integration	Limited	Full Spring ecosystem
Best For	Legacy maintenance	New projects

18. Tiles Integration

Templating via tiles-defs.xml: define layouts (header, footer, body), map to action forwards. Reusable layouts, consistent look, easier UI updates.

19. Dependency Injection in Struts

Struts 1: no native DI. Struts 2: struts2-spring-plugin injects dependencies into Actions. OrderService injected into OrderAction → cleaner, testable.

20. Struts 1 → 2 Migration Steps & Challenges

1. Rewrite Actions as POJOs
2. Replace ActionForms with domain objects
3. Redesign validation (XML → annotations/interceptors)
4. Update config (struts-config.xml → struts.xml packages)
5. Migrate JSP tags (Struts 1 → Struts 2 UI tags)
6. Adapt to OGNL & interceptor model

Challenges: deprecated features, custom RequestProcessor logic, form binding changes. Payoff: cleaner architecture, extensibility, lower maintenance.

21. Configuration File Structure & Maintainability

Struts 1: single large struts-config.xml → hard to maintain. Struts 2: modular struts.xml per package/module (e.g., inventory-struts.xml, finance-struts.xml) + annotations.

22. Validator Framework

XML-defined rules (required, email, length) + auto JavaScript generation. Dual client/server validation. Reduces boilerplate, ensures consistency.

23. ValueStack in Struts 2

Per-request data stack: Action properties, temp objects, OGNL-accessible. Layered structure ensures correct value resolution. <s:iterator value="products"> retrieves list directly — decouples view from controller.

24. Session Management: Struts vs Servlet API

Struts 1: session-scoped ActionForms. Struts 2: SessionAware interface injects session map via interceptor. Type-safe, less boilerplate than raw HttpSession.

25. Interceptor Stacks для Cross-Cutting Concerns

Configurable interceptor collections per package/action. Financial module: strict stack (audit, auth, encryption). Public catalog: lightweight stack. Modular, maintainable.

26. ActionErrors & ActionMessages (Struts 1)

Собирают multiple error/success messages; display via <html:errors>/<html:messages>. Clean logic/presentation separation.

27. Multi-Module Configuration

Struts 1: separate configs per URL prefix (admin, user, reporting). Struts 2: packages. Benefits: isolation, parallel dev, independent deploy/test.

28. DispatchAction Variants & Code Optimization

Class	Method Selection	Best For
DispatchAction	Request parameter	CRUD
LookupDispatchAction	Resource key → method map	i18n forms
MappingDispatchAction	Action mapping	Complex routing

Consolidates related ops into one class.

29. Result Types & Navigation Flexibility

Selection factors: flow, performance, security, content type. redirect prevents resubmit; dispatcher faster for internal; stream for PDF/downloads.

30. Struts 2 Action Lifecycle vs Struts 1

Struts 2: FilterDispatcher → ValueStack init → Interceptor Stack (params, validation, etc.) → Action execute → Interceptor post-processing → Result render. Key differences: POJO Actions, no ActionForm, interceptors replace monolithic RequestProcessor.

Пример: PurchaseAction: auth interceptor → validation interceptor → logging interceptor → Action → result.

🔍 Real-World Scenario Questions (Behavioral & Situational)

No contractions; required phrases used exactly once each.

1. Explain Struts framework & enterprise use.

Expect: MVC, separation of concerns, enterprise benefits.
Answer: "Struts is a Java-based web application framework that follows the Model-View-Controller architecture. It is used in enterprise applications because it provides centralized configuration, reusable components, and a clear separation of concerns. These features help teams maintain large-scale applications more efficiently."

2. MVC within Struts?

Expect: ActionServlet, Action, JSP roles.
Answer: "In Struts, the controller is managed by the ActionServlet, which receives user requests and routes them to the appropriate Action class. The model contains the business logic and data handling, while the view uses JSPs to present the processed information. This structure improves maintainability and reduces coupling."

3. Purpose of struts-config.xml?

Expect: Configuration-centric knowledge.
Answer: "The struts-config.xml file holds the core application configuration, including form beans, global forwards, action mappings, and controller settings. It allows developers to manage request flow and component interactions from a single centralized file."

4. ActionForm role & when to use?

Expect: Form handling, validation.
Answer: "ActionForm is a JavaBean used to capture and validate user input before it reaches the Action class. It is used when an application requires structured form data and input validation before the controller processes the request."

5. Challenging issue resolved in Struts app?

Expect: Technical obstacle resolution.
Answer: "In my previous role, I encountered an issue where form validation was not triggering correctly due to an incorrect mapping in the struts-config.xml file. I traced the problem using detailed logging, corrected the mapping, and enhanced the validation logic to prevent similar issues from reoccurring."

6. Code quality & maintainability in legacy Struts?

Expect: Best practices for older frameworks.
Answer: "I focus on modularizing Action classes, removing duplicated logic, and adding clear documentation. I also introduce unit tests to verify business logic. These practices help improve stability and reduce risk in legacy environments."

7. Troubleshoot form data not submitting correctly.

Expect: Logical debugging steps.
Answer: "I would begin by verifying that the form fields match the ActionForm property names. Then I would check the action mapping in struts-config.xml to ensure that the form bean is correctly associated. If needed, I would enable debugging logs to trace request parameters and identify where the data flow breaks."

8. Tight deadlines, multiple Struts modules.

Expect: Prioritization, organization under pressure.
Answer: "At a previous position, I handled this situation by breaking tasks into smaller deliverables, prioritizing based on business impact, and communicating status updates to stakeholders. This approach ensured that all modules received attention without compromising quality."

9. Migrate Struts to Spring MVC?

Expect: Migration strategy, risk mitigation.
Answer: "I would first assess the existing modules to identify dependencies and complexity. Then I would design an incremental migration strategy that replaces Struts controllers with Spring components while keeping the application functional. Proper documentation and testing would ensure a smooth transition."

10. Cross-functional collaboration to improve Struts app?

Expect: Communication, teamwork, coordination.
Answer: "At my previous job, I collaborated with QA, UI designers, and backend developers to optimize request handling in a Struts module. Our coordination improved the response time, enhanced the UI flow, and reduced defects in the subsequent release."