Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

paulcwarren / spring-content Public

Notifications You must be signed in to change notification settings
Fork 67
Star 277

Code
Issues 14
Pull requests 12
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

fix: events should only be published once per content operation#1901

Merged

paulcwarren merged 23 commits intomainpaulcwarren/spring-content:mainfrom fix/issue-1869paulcwarren/spring-content:fix/issue-1869Copy head branch name to clipboard

May 7, 2024

+270-203

Conversation Commits23 (23)Checks Files changed

Commits

Commits on May 3, 2024

fix: events should only be published once per content operation
paulcwarren
committed
event handler methods need to match store package
paulcwarren
committed
setContent should only call aftersetcontent events once only
paulcwarren
committed
Switch back to spring-content-examples main branch
paulcwarren
committed
need to check spring-content first
paulcwarren
committed
assert entityClass and contentIdClass are non-null
paulcwarren
committed
exit early if either class is null
paulcwarren
committed
Add some logging so we can see if afterPropertiesSet is being called
paulcwarren
committed
more logging around the placement service default converters
paulcwarren
committed
more logging in azure storage impl to see what the typedescriptor of the classes being converted look like
paulcwarren
committed
log the conversionservice and its converters
paulcwarren
committed
Log the placement service's hashcode so we cancheck if the storage impl has the same instance as the one that is initially configured
paulcwarren
committed
wip: more logging
paulcwarren
committed
wip: more logging around converters getClassHierarchy to see if the problem is there
paulcwarren
committed
Temporarily make placementserviceimpl an impl of genericconversionservice so we can add logging
paulcwarren
committed
add a default set of converters
paulcwarren
committed
temporarily disable NaturalIdIT test
paulcwarren
committed
add a toString to placement service for better logging
paulcwarren
committed
even more logging
paulcwarren
committed
Call convert with the same type descriptors as used for the canConvert call
paulcwarren
committed
Re-instate the original placement service
paulcwarren
committed
fix NPE
paulcwarren
committed
Add logging in s3 reactive storage where content id and length are set
paulcwarren
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.