-
1. Re: Sending Java Objects using RemoveInvoker
dward Apr 19, 2013 10:45 AM (in response to kostas_papag)For an object to be serializable by SwitchYard, it either needs to adhere to the javabeans specification, or it has to use SwitchYard-provided annotatations, as per the documentation.
That being said, there are several Java API classes that are handled specially, even though they aren't javabeans. Unfortunately, UUID is not one of them. Whereas I could add direct support for UUID, obviously I can't do this for every non-javabean in the Java API.
You do have an option, though. You can mark the Offer class with a @Strategy(access=AccessType.FIELD), but then store the UUID as a member variable of type String. Then, your set/getUUID() methods would convert the String to/from a UUID using UUID's toString()/fromString() methods.
-
2. Re: Sending Java Objects using RemoveInvoker
kostas_papag Apr 22, 2013 8:58 AM (in response to kostas_papag)Thanks for the quick reply and the suggestion! We probably going for your proposal. Some kind of API could be useful for serialization/deserialization cause working with 3rd party libraries can be kind of cumbersome.
-
3. Re: Sending Java Objects using RemoveInvoker
dward Apr 30, 2013 11:11 AM (in response to dward)I've added a jira for this: SWITCHYARD-1451
-
4. Re: Sending Java Objects using RemoveInvoker
dward Jun 4, 2013 3:05 PM (in response to dward)There is now a pull request for this: SWITCHYARD-1451.