JMS Converter

PHP Converters Serializers Deserializers

Installation

composer require ecotone/jms-converter

Ecotone comes with integration with JMS Serializer and extending it with extra features.

Module Powered By

Great library, which allow for advanced conversion between types JMS/Serializer.

Native Conversion

Ecotone with JMS will do it's best to deserialize your classes without any additional configuration needed. Suppose we have JSON like below:

{
    "personName": "Johny",
    "address": ["street": "A Good One", "houseNumber": 123
}

$this->commandBus->sendWithRouting(
   "settings.change", 
   '{"personName": "Johny","address":["street":"A Good One","houseNumber":123}',
   "application/json"
)

Then, suppose we have endpoint with following Command:

#[CommandHandler]
public function changeSettings(ChangeSettings $command)
{
   // do something
}

class ChangeSettings
{
    private string $personName;    
    private Address $address;
}

class Address
{
    private string $street;
    private string $houseNumber;
}

No need for any configuration, deserialization and serialization will be handled for you.

Array Deserialization

In order to deserialize array you must provide type hint.

/**
* @var Product[]
*/
private array $products;

This will let JMS know, how to deserialize given array. In order to deserialize array of scalar types:

/** @var string[] */
private array $productNames;
=>
["milk","plate"]

If your array is hash map however:

/** @var array<string,string> */
private array $order;
=>
["productId":"fff123a","productName":"milk"]

If you've mixed array containing scalars, then you may use ArrayObject to deserialize and serialize it preserving keys and types.

private \ArrayObject $data;
=>
["name":"Johny","age":13,"passport":["id":123]]

Custom Conversions for Classes

With Native Conversion, we take full control of how specific classes are serialized and deserialized. We can call factory methods that validate data correctness, apply business rules, or set intelligent defaults based on our domain logic. This is especially useful when converting between complex objects and simple types like strings or integers—for example, turning a Money value object into an integer for storage, or reconstructing it with proper validation when loading, ensuring given Object is always in valid state.

JMS Converter make use of Converters registered as Converters in order to provide all the conversion types described in Conversion Table. You can read how to register newConverter in Conversion section.

Example usage

If we want to call bus with given JSON and deserialize productIds to UUID:

$this->commandBus->sendWithRouting(
   "order.place",  
   '{
       "productIds": ["104c69ac-af3d-44d1-b2fa-3ecf6b7a3558"], 
       "promotionCode": "33dab", 
       "quickDelivery": false
   }',
   "application/json"
)

Then, suppose we have endpoint with following Command Handler:

#[CommandHandler('order.place')]
public function placeOrder(PlaceOrder $command)
{
   // do something
}

and related Command:

class PlaceOrder
{
    /**
     * @var Uuid[]
     */
    private array $productIds;
    
    private ?string $promotionCode;
    
    private bool $quickDelivery;
}

Then as product Ids is array of Uuid, we can use customer Converter to define how to convert from string to Uuid, and vice versa (if needed):

class ExampleConverterService
{
    #[Converter]
    public function convert(string $data) : Uuid
    {
        return Uuid::fromString($data);
    }
    
    #[Converter]
    public function convert(Uuid $data) : string
    {
        return $data->toString();
    }
}

Serialization Customization

If you want to customize serialization or deserialization process, you may use of annotations on properties, just like it is describes in Annotation section in JMS Serializer.

class GetOrder
{
   /**
   * @SerializedName("order_id")
   */
   private string $orderId;
}

Configuration

Register Module Conversion

class Configuration
{
    #[ServiceContext]
    public function getJmsConfiguration()
    {
        return JMSConverterConfiguration::createWithDefaults()
                ->withDefaultNullSerialization(false) // 1
                ->withNamingStrategy("identicalPropertyNamingStrategy"); // 2
                ->withDefaultEnumSupport(true) // 3
    }
}

withDefaultNullSerialization

Should nulls be serialized (default: false)

withNamingStrategy

Serialization naming strategy ("identicalPropertyNamingStrategy"/"camelCasePropertyNamingStrategy", default: "identicalPropertyNamingStrategy")

withDefaultEnumSupport

When enabled, default enum converter will be used, therefore Enums will serialize to simple types (default: false)

Serialize Nulls for specific conversion

If you want to make convert nulls for given conversion, then you can provide Media Type parameters

$this->serializer->convertFromPHP(
    ["id" => 1,"name" => null], 
    "application/json;serializeNull=true"
)

=>

{"id":1,"name":null}

Conversion Table

JMS Converter can handle conversions:

// conversion from JSON to PHP
application/json => application/x-php | {"productId": 1} => new OrderProduct(1)
// conversion from PHP to JSON
application-x-php => application/json | new OrderProduct(1) => {"productId": 1}

// conversion from XML to PHP
application/xml => application/x-php | <productId>1</productId> => new OrderProduct(1)
// conversion from PHP to XML
application-x-php => application/xml | new OrderProduct(1) => <productId>1</productId>

// conversion from JSON to PHP Array
application/json => application/x-php;type=array | {"productId": 1} => ["productId": 1]
// conversion from PHP Array to JSON
application/x-php;type=array => application/json | {"productId": 1} => ["productId": 1]

// conversion from XML to PHP Array
application/xml => application/x-php;type=array | <productId>1</productId> => ["productId": 1]
// conversion from PHP Array to XML
application/x-php;type=array => application/xml | ["productId": 1] => <productId>1</productId>