serverless / serverless/examples

unable to test java application in serverless offline

Open
#575 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
11.5k
Forks
4.4k
Avg merge
2h 55m
Merged PRs (30d)
3

Description

Hi All
I have created a server less application using java,dynamodb and API gatway. i want to test this functionality in local using serverless offline framework. But i am facing the following issue while invoking the API. Please help me to resolve this issue.
offline: Starting Offline: dev/eu-west-1.
┌─────────────────────────────────────────────────────────────────────────┐
│ │
│ GET | http://localhost:3000/dev/hello │
│ │
└─────────────────────────────────────────────────────────────────────────┘enter code here
offline: GET /dev/hello (λ: hello)
offline: Failure: EISDIR: illegal operation on a directory, open 'C:\Users\saswat\AppData\Local\Temp\serverless-offline\services\example\hello\ckivvmja30
00254ty13fi3ks1\code\com\serverless'
Error: EISDIR: illegal operation on a directory, open 'C:\Users\saswat\AppData\Local\Temp\serverless-offline\services\example\hello\ckivvmja3000254ty13fi
3ks1\code\com\serverless'

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report mentions a Java serverless application, the GET /dev/hello entry point, and a Windows serverless-offline temporary path, but names no repository file or test. Start by locating the Java example and its offline configuration, then reproduce the request on Windows. Done means the endpoint runs locally without the reported EISDIR failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend, database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.