Replace pubsub+ naming #172
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Included JSON tutorial but left out AVRO and generic as they are essentially identical
hand crafted spelling errors Co-authored-by: Copilot <[email protected]>
…ace-dev-tutorials into jcsmp-serdes-feature
|
Please mark whether you used Copilot to assist coding in this PR
|
TamimiGitHub
reviewed
Oct 3, 2025
| * Client-profile enabled with guaranteed messaging permissions. | ||
|
|
||
| One simple way to get access to Solace messaging quickly is to create a messaging service in Solace PubSub+ Cloud [as outlined here](https://solace.com/products/event-broker/cloud/). You can find other ways to get access to Solace messaging below. | ||
| One simple way to get access to Solace messaging quickly is to create a messaging service in Solace Solace Cloud [as outlined here](https://solace.com/products/event-broker/cloud/). You can find other ways to get access to Solace messaging below. |
There was a problem hiding this comment.
I dont think this should be Solace Solace...
TamimiGitHub
reviewed
Oct 3, 2025
| * Using the APIs | ||
|
|
||
| Using the Solace PubSub+ APIs to provision an endpoint can be a convenient way of getting started quickly without needing to become familiar with the management interface. This is why it is used in this tutorial. However it should be noted that the management interface provides more options to control the queue properties. So generally it becomes the preferred method over time. | ||
| Using the Solace Solace Messaging APIs to provision an endpoint can be a convenient way of getting started quickly without needing to become familiar with the management interface. This is why it is used in this tutorial. However it should be noted that the management interface provides more options to control the queue properties. So generally it becomes the preferred method over time. |
Mrc0113
reviewed
Oct 3, 2025
There was a problem hiding this comment.
Pull Request Overview
This PR updates product naming throughout the documentation by replacing "PubSub+" references with "Solace" in appropriate contexts. The changes standardize terminology to align with current Solace product naming conventions, improving consistency across the developer documentation.
- Replace "Solace PubSub+ API" with "Solace Messaging API"
- Update "PubSub+ Manager" to "Broker Manager"
- Change "PubSub+ Event Broker" to "Solace Event Broker"
Reviewed Changes
Copilot reviewed 59 out of 61 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| src/pages/tutorials/tanzu/*.md | Updated Pivotal Cloud Foundry tutorial naming from PubSub+ to Solace terminology |
| src/pages/tutorials/spring/*.md | Modified Spring framework tutorial references to use Solace naming |
| src/pages/tutorials/semp/*.md | Updated SEMP API tutorial documentation with current product names |
| src/pages/tutorials/rest-messaging/publish-subscribe.md | Changed REST messaging tutorial to use Solace Event Broker terminology |
| src/pages/tutorials/openmama/hello-world.md | Updated OpenMAMA integration tutorial naming |
| src/pages/tutorials/nodejs/*.md | Modified Node.js tutorial references to current Solace naming |
| src/pages/tutorials/jms/*.md | Updated JMS tutorial documentation with Broker Manager references |
| src/pages/tutorials/jcsmp/*.md | Changed JCSMP tutorial naming and updated sample repository commit |
| src/pages/tutorials/javascript/*.md | Modified JavaScript tutorial references to current naming |
| src/pages/tutorials/java*/*.md | Updated Java-related tutorial naming conventions |
| src/pages/tutorials/dotnet/*.md | Changed .NET tutorial references to Broker Manager |
| src/pages/tutorials/c/*.md | Updated C API tutorial naming to Solace Event Broker |
| src/pages/404.js | Updated 404 page references to Solace Event Broker |
| src/components/*.js | Modified component references to use current Solace naming |
| gatsby-config.js | Updated JCSMP samples repository commit reference |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
With the Solace Solace fixes in place can you merge @TamimiGitHub or shall I? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I completed this change with Claude and some
sedcommands so I am moving it to a new PR so that we can do some more extensive testing on it before applying it to the public site. Claude and I did not make any changes to paths, urls, code snippets or links to code that may be broken by a change from PubSub+ convention.I clicked through every tutorial page on my local running copy and everything seems to be functioning normally. But lets not merge this change till monday at the earliest