OBEX defines the operations: CONNECT, PUT, GET, SETPATH etc. The services/profiles then define which of those operations must be supported. The operations have the same formats and protocols regardless of the application[1].
Note that the GetFolderListings application prompts at start-up whether to connect to the Folder-Browsing or Inbox service. That simply sets what network endpoint to connect to[2], and what OBEX Target to CONNECT to. After the connection is made there is absolutely no difference in the application's behaviour. If one tries a GET on an default/inbox OBEX server the app+library will start the operation as normal but the server will likely just return an error code.
Andy
[1] Folder-Browsing: "is built using OBEX PUT, GET and SETPATH commands as
well as the OBEX Folder-Listing object.", whereas the Inbox service
only needs to support CONNECT, PUT and DISCONNECT.
[2] For IrDA, ServiceName "OBEX" is used for both. For Bluetooth the two different UUIDs are used (in UUID16 form: 0x1105 and 0x1106).