Skip to content

Conversation

@a-bx
Copy link

@a-bx a-bx commented Jul 8, 2019

Estos fixes solo se preocupan de mantener la comunicación entre el cliente SOAP de un WSDL viejo y el servicio en Rails. No entregan un WSDL Válido.

Es decir, hace que se reconozca un request desde un cliente y que el response sea un XML válido

@a-bx a-bx changed the title Fixes para funcionar con WSDL estándar Fixes Jul 10, 2019
vsanchez-meli
vsanchez-meli approved these changes May 7, 2021
Copy link

@ntorresj ntorresj left a comment

Choose a reason for hiding this comment

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

👍 es bien

@rdiaz-meli
Copy link

LBQEABX

Copy link

@JotaSe JotaSe left a comment

Choose a reason for hiding this comment

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

LGTM

end

default_response_tag = soap_config.camelize_wsdl ? 'Response' : '_response'
default_response_tag = 'Response'

Choose a reason for hiding this comment

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

Creo que esto debería estar freeze o ser un sym, si no se crean objetos en memoria que el GC de ruby va a tener que salir a allocar en tiempo de request.

Choose a reason for hiding this comment

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

end
xml.tag! "soap:Body" do
xml.tag! "tns:#{@action_spec[:response_tag]}" do
xml.tag! "SOAP-ENV:Body" do

Choose a reason for hiding this comment

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

Estamos exponiendo el Body del tag SOAP-ENV y esto pudiera ofender al tag por hacer Body Shamming

@despinozac
Copy link

La rama master es ofensiva, sugiero ocupar algo menos ofensivo como main o principalits

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.