Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve operation and param element generation #16

Merged
merged 1 commit into from
Jul 20, 2024

Conversation

veewee
Copy link
Member

@veewee veewee commented Jul 19, 2024

Q A
Type bug
BC Break no
Fixed issues #15

Fixes #15

Summary

@@ -38,7 +38,7 @@ protected function calculateParam(): mixed
#[Test]
public function it_is_compatible_with_phps_encoding()
{
static::markTestSkipped('Literal document seems about right - yet php soap uses the type instead of the part name. Not sure what to do here yet.');
static::markTestSkipped('Literal document seems about right - it seems to be taking the param name instead of the complextype name though. Not sure what to do here yet.');
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO : Check spec for literal encoding on what to do here.
Current assumption:

  • if the type is a complex type, the parameter name is being used (unqualified)
  • if the type is an element type, the element info is being used (qualified)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cant seem to figure out why it is encoding it like this. SOAP-UI is also using the message part name. Leaving it for now.

@veewee veewee force-pushed the fix-operation-message-names branch from 5a2f04d to 21772ef Compare July 19, 2024 13:11
@veewee veewee merged commit 39e438c into php-soap:main Jul 20, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Names of elements in soap:body are incorrect
1 participant