use dspace.url to dspace.server.url

[Paurikova2]

Phases	MP	MM	MB	MR	JM	Total
ETA	0	0	0	0	0	0
Developing	0.2	0	0	0	0	0
Review	0	0	0	0	0	0
Total	-	-	-	-	-	0
ETA est.						0
ETA cust.	-	-	-	-	-	0

Problem description

There are some uses of the property 'dspace.url'. Use 'dspace.server.url' instead.

Summary by CodeRabbit

• Chores
  • Adjusted the server URL retrieval to ensure consistent handling of server addresses.
• Documentation
  • Updated example URLs in API references to reflect the new server URL information.

[coderabbitai]

Walkthrough

The changes update the configuration property used for constructing URLs in two components. In the API module, the method retrieving the URL now uses the "dspace.server.url" property instead of "dspace.url". Similarly, the REST controller’s JavaDoc examples have been updated to replace the {dspace.url} placeholder with {dspace.server.url}. No public entities or method logic have been altered.

Changes

File(s)	Change Summary
dspace-api/src/main/java/…/DSpaceApi.java dspace-server-webapp/src/main/java/…/HdlResolverRestController.java	Replaced references to "dspace.url" with "dspace.server.url". In the API, this updates the URL used for handle registration, while in the REST controller, the JavaDoc request examples now use the updated placeholder.

Poem

🐇 In code’s garden, I hop with glee,
A tiny change sets our URLs free.
From "dspace.url" to the server so bright,
Our docs and API now shine in the light.
A rabbit’s cheer for a cleaner view—
Happy updates to all, from me to you!
🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ec96cb4 and 12e654e.

📒 Files selected for processing (2)

• dspace-api/src/main/java/org/dspace/api/DSpaceApi.java (1 hunks)
• dspace-server-webapp/src/main/java/org/dspace/app/rest/hdlresolver/HdlResolverRestController.java (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: dspace-dependencies / docker-build (linux/amd64, ubuntu-latest, true)
• GitHub Check: Run Integration Tests
• GitHub Check: Run Unit Tests

🔇 Additional comments (4)

dspace-server-webapp/src/main/java/org/dspace/app/rest/hdlresolver/HdlResolverRestController.java (3)

91-91: Documentation update looks good

The JavaDoc example URL now references the correct property name {dspace.server.url} instead of {dspace.url}, which aligns with the PR objective of standardizing on dspace.server.url.

---

121-121: Documentation update looks good

The JavaDoc example URL has been updated to use {dspace.server.url} consistent with the standardization effort.

---

147-147: Documentation update looks good

The JavaDoc example URL has been properly updated to use {dspace.server.url} consistent with the other documentation changes.

dspace-api/src/main/java/org/dspace/api/DSpaceApi.java (1)

99-99:

Details

✅ Verification successful

Code update looks good

The property retrieval has been correctly updated from "dspace.url" to "dspace.server.url" which aligns with the PR objective of standardizing on using dspace.server.url throughout the codebase.

---

🏁 Script executed:

#!/bin/bash
# Check if there are any remaining instances of dspace.url in the codebase
# that might need to be updated for consistency

# Search for remaining instances of dspace.url in Java files
echo "Searching for remaining instances of 'dspace.url' in Java files:"
rg "dspace\.url" --type java

# Search for dspace.server.url to understand usage patterns
echo "Checking usage patterns of 'dspace.server.url':"
rg "dspace\.server\.url" --type java -C 1

Length of output: 66738

---

Review Approval: Consistent Usage of "dspace.server.url" Confirmed

The update is verified—there are no lingering references to "dspace.url" in the codebase, and usage has been standardized to "dspace.server.url" across all modules (including the updated DSpaceApi.java at line 99).

• No stray instances of "dspace.url" were found.
• Consistent application of "dspace.server.url" is evident throughout the project.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[milanmajchrak]

Consider using of the dspace.ui.url. Check the issue comments

[Paurikova2]

This solution did not help solve the problem.
fix: #906