Oracle JDeveloper 12c中OSB导入WSDL无指定端点的问题咨询

It sounds like the deployed SayHello composite isn't showing up in your JDeveloper server connection tree, which is why you can't locate the makegreeting_client_ep(ws) endpoint. Here are the most likely causes and actionable fixes to try:

1. Verify the SayHello Composite is Successfully Deployed #

• First, check if the SayHello SOA composite was actually deployed to your DefaultServer. Look at JDeveloper's Deployment tab (bottom of the IDE) for any errors during deployment—failed deployments won't appear in the server tree.
• You can also confirm via the WebLogic Server Console (typically at http://localhost:7001/console): Navigate to Deployments and check if SayHello[Default 1.0] is listed and in an "Active" state. If it's missing, redeploy the composite and resolve any deployment errors first.

2. Validate Your Server Connection Configuration #

• Ensure your JDeveloper server connection points to a fully configured SOA/OSB domain. If your domain was created without the SOA Suite or OSB templates, SOA composites won't appear in the tree.
• Right-click your server in the Application Servers view, select Properties, and confirm the connection is linked to a SOA-enabled domain. Also, make sure the server is running (green arrow next to the server name) and the connection is active.

3. Confirm the Composite's WSDL is Exposed #

• Log into the Enterprise Manager (EM) console (usually at http://localhost:7001/em), navigate to the SayHello composite, and check if its WSDL endpoint is enabled. Sometimes composites deploy but have endpoints disabled by default.
• If the WSDL is accessible, try importing it directly via URL instead of browsing the server tree. Use the HTTP endpoint (e.g., http://<server-host>:7101/SayHello/makegreeting_client_ep?wsdl)—this bypasses the tree navigation issue and lets you select the correct HTTP port directly.

4. Check for Domain/Version Compatibility #

• Ensure your JDeveloper version (12.2.1.3.0) matches the WebLogic Server, SOA, and OSB versions in your domain. Mismatched versions can cause unexpected behavior in the server connection tree.
• Double-check that you included both the SOA Suite and Oracle Service Bus templates when creating your domain. Missing either template will prevent composites from appearing in JDeveloper.

If none of these steps work, try restarting both your WebLogic Server and JDeveloper, then redeploy the SayHello composite and refresh the server connection (right-click the server, select Refresh).

内容的提问来源于stack exchange，提问作者Tri