eclipse-ee4j / eclipse-ee4j/metro-wsit

Provide some means to make the ServletContext accessible in general, i.e. when NOT currently executing a Web Service request

Open
#332 0 comments 0 reactions 0 assignees View on GitHub
Component: jaxws-runtime ERR: Assignee Priority: Major Type: Improvement
Dominant language
Java
Stars
6
Forks
21
Avg merge
10h 2m
Merged PRs (30d)
1

Description

Actually the ServletContext of a deployed WS is accessible in a WS by means of the inejected @Resource. Injection of the @Resource WebServiceContext works fine, but accessing the ServletContext from there only works in the WS methods but not in the startup / init phase.

Seealso in discussion board: [http://www.java.net/forum/topic/glassfish/metro-and-jaxb/access-servletcontext-jax-ws-web-service-0](http://www.java.net/forum/topic/glassfish/metro-and-jaxb/access-servletcontext-jax-ws-web-service-0)

Source: [https://github.com/javaee/metro-wsit/issues/1515](https://github.com/javaee/metro-wsit/issues/1515)
Author: glassfishrobot

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the WebServiceContext @Resource behavior described in the issue, especially the difference between Web Service methods and the startup/init phase. Read the linked discussion and source issue #1515 to determine the intended access mechanism and how completion should be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.