Serialization with 6.0

Hi,
My application is using Externalization and Weblogic 5.x RMI. This has been
working fine until I upgraded to weblogic6.0
Now my serialization is broken and no matter what, I have not been able to
find the reason for it. If simply gives me EOF exception. If I go for java
default serialization then the problem objects get serialized properly (but
I cannot change as too much of my code is tied to Externalization).
Is there any change in the way weblogic6.0 is handling the serialization?
I will appreciate any insight on this matter.
Thanks,
Sushil

Yes, it works with JDK1.3 on WLS5.x RMI.
In fact I found the problem too.
The write(int b) of ObjectOutput writes a byte. It seems weblogic5.x was
overriding this method to write int.
My code was using this method to write number of bytes that I was going to
write next and then corresponding read to read the number of bytes coming
and allocate a byte array of that length.
With weblogic 6, it seems that the override is gone (which is good but
without any documentation this gives developers such problems!).
The problem got more confusing when even after making this change things
didn't work and my code was throwing EOF exception exactly at the same
point. But by that time I had too many more changes in my code. So after one
frustrating week, I started afresh on Monday with just this change and it
worked.
Sushil
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]..
Does it work with JDK 1.3 on WLS 5.x RMI?
Can you show us your writeExternal and readExternal implementations?
-- Rob
Sushil Goel wrote:
Hi,
My application is using Externalization and Weblogic 5.x RMI. This has
been
working fine until I upgraded to weblogic6.0
Now my serialization is broken and no matter what, I have not been ableto
find the reason for it. If simply gives me EOF exception. If I go forjava
default serialization then the problem objects get serialized properly(but
I cannot change as too much of my code is tied to Externalization).
Is there any change in the way weblogic6.0 is handling theserialization?
>>
I will appreciate any insight on this matter.
Thanks,
Sushil

Similar Messages

'Payload not Serializable' with custom WSDL data types in message-style web service

I'm implementing a message-style web service which publishes to a JMS Queue.
I had the web service built and deployed, but noticed that the "sendRequest" message's
part was of type "xsd:anyType." This is not specific enough for our interface,
since it is externally facing and needs to describe the object we're expecting
on the back end.
So I replaced xsd:anyType with mynamespace:MyType, which is defined as a complex
type in the same WSDL document.
My problem is that when I test the web service with the new WSDL (using the client.jar),
I get a server-side exception from the DestinationSendAdapter.doPost() method.
The exception reads:
javax.servlet.ServletException: Payload not Serializable
at weblogic.soap.server.servlet.DestinationSendAdapter.doPost(DestinationSendAdapter.java:129)
The domain object ('classic' JavaBean) that it should map to on the server side
extends a class that implements Serializable, so it should inherit the trait.
So my questions are:
1) Did I properly go about trying to restrict the object type that gets sent to
my Destination?
2) If no, what is the correct way? If yes, why am I receiving the Payload not
Serializable error if the domain object implements Serializable?
Thanks in advance.

Resolved:
Apparently this is the right approach, as it boiled down to a classpath issue
on the client-side. Thanks anyway.

++Custom Serialization with Complex Data type (Nested Classes)

Hi,
We have a scenario wherein we need to write CUSTOM SERIALIZERS for complex datatypes like INVOICE & ORDER (INVOICE inturn has ADDRESS type among others, ORDER has ADDRESS type, a COLLECTION of type ORDERITEM each of which are Java Classes in themselves)
The example of Custom Serializer given in the SOA AS Dev Guide http://download.oracle.com/docs/cd/B31017_01/web.1013/b28975/custserial.htm#CFHHIBCA)
shows only a simple java type used for serialization and deserialization.
Can anyone please help us out by sharing any example depicting the CUSTOM SERIALIZERs for COMPLEX DATA TYPES?
Thanks in advance,
Pavan.

Hello,
Could you please post the code of your classes in the forum (at least the interfaces) ?
Regards
Tugdual Grall

POF serialization with replicated cache?

Sorry again for the newbie question.
Can you use POF serialized objects in a replicated cache?
All of the examples show POF serialized objects being used with a partitioned cache.
If you can do this, are there any caveats involved with the "replication" cache? I assume it would have to be started using the same configuration as the "master" cache.

Thanks Rob.
So, you just start up the Coherence instance on the (or at the) replication site, using the same configuration as the "master"? (Of course with appropriate classpaths and such set correctly)

Serialization with dynamic classloader

i have the following problem:
i load a serialized object from a file. This object's classes are are in a folder , witch is not in CLASSPATH, and so the classes are not loaded when i try to read objects from the file.
I loaded this classes with my class loader , but i still get an error when a read the object from the file.
I lookt all day for an example, so any help is apreciated.
Thx

As a guess you need to create your own version of ObjectInputStream and overload some of the methods in it - like resolveClass()
There are a number of threads that are returned using the search string "resolveClass ObjectInputStream"
Loking at a couple I found this...
http://forum.java.sun.com/thread.jspa?forumID=4&threadID=468339

Registering CS6 serialization with AAMEE

Hi!
I just downloaded and am trying to setup serialization for nearly 1000 machines running CS6 Master Collection on our base image (win 7, sysprepped.) I've downloaded AAMEE 3.0 and when I run it to create the serialization executable as shown in the deployment guide, I receive the following errors:
5/29/2012 09:25:35[INFO] AdobePackageBuilder - Build Version - 3.0.166.0
5/29/2012 09:25:35[INFO] AdobePackageBuilder - Logging Level verbosity Set to 4
5/29/2012 09:25:35 [WARN] AdobePackageBuilder - Error in processing the UpdatesInfo tag.
Does anyone know what this means, and how I go about resolving it? I'm using the same Adobe user id as I am here in the forum, and the serial number does work on a single install.
Thanks in advance!
-brad

r_baiswar wrote:
Hi,
"Error in processing the UpdatesInfo tag" warning doesnt have any impact on package creation or deployment.
About another issue that "product is asking for adobe id login on launch" - can you please share exact steps performed for deployment and packaging. this will help us in reproducing and debugging this issue.
thanks,
Rahul | [email protected]
Come on Adobe...we need an answer for the "Error in processing the UpdatesInfo tag" error.
We have enterprise users waiting for us to deploy your software, please don't ignore this issue.
Ignoring the issue does ot resolve the issue.
TIA,
Don

Serialization with ChunkedObjectInputStream. Sometimes yes sometimes no.

I'm working on a system that's built on Weblogic 7 sp4 and for some reason whenever the app server is setup in a clustered manner I've noticed that object serialization fails but in such a way that if there's a delay involved after the writeObject before the readObject. It works. But whenever there's little delay is doesn't work even though if you inspect
          the contents of the stream's chunk you can quite clearly see from the data stream that the data is there.
          Basically it's using ChunkedObjectInputStream because it's marshalling parameters over the wire in a custered environment.

Can you duplicate this at will. Do you have a test case which I can use to duplicate it?
          This is quite strange but , if there is a way to duplicate this problem , I will try to see if I can identify the root cause.
          Please tell me the JVM you are using as well.
          sree

Java 5 Enums serialization with XMLEncoder...

Hello,
I'd like to know why a bean attribute whose type is a Java 5 enum is
not saved when using XMLEncoder. This field is in fact ignored...
Anybody knows how to persist such fields using standard JDK (I mean
no third party library) ?
public enum TestBeanEnum {
    R160x100,
    R320x200,
    R640x480,
    R800x600,
    R1024x768,
    R1280x1024,
    R1600x1200;
public class Setup {
    private TestBeanEnum a0;
    private boolean a1;
    public Setup() {
    public boolean isA1() {
        return a1;
    public void setA1(boolean a1) {
        this.a1 = a1;
    public TestBeanEnum getA0() {
        return a0;
    public void setA0(TestBeanEnum a0) {
        this.a0 = a0;
    private static void save(Setup setup, File file) throws IOException {
        FileOutputStream out = new FileOutputStream(file);
        XMLEncoder encoder = new XMLEncoder(out);
        encoder.writeObject(setup);
        encoder.close();
        out.close();
...Only the attribute a0 is not saved all over, even relatively complex data
types are automatically persisted.
I also find a strange behavior, the keyword "transient" seems to be ignored
by the XMLEncoder and a transient field is made persistent !!!
Did I miss something ? Is this strange behavior a bug ?
Thanks for all,
David Crosson.

looks like a bug to me
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5015403

EJB + JPub = Serializable ?!

Today I use Oracle objects with JPub and no any problems has occupied before. But now I intend for build EJB that use JPub produced classes, and the main problem is the JPub produced classes not serializable. Of course I try to subclass those classes and implements on them java.io.Selializable on both oracle.sql.Datum and java.sql.SQLData but marshaling error still present.
My question is: if I pass to the client from EJB instance any object, this object must be one of the following class: String, BigDecimal, or user defined class contains only Selializable field? And I cannot use objects passed by value with classes like oracle.jpub.runtime.MutableStruct or java.sql.Array? If yes, that is mean JPub not useful tool for EJB development, and I must provide my own classes for my Oracle Objects that implements java.io.Serializable with only Serializable fields?
null

Today I use Oracle objects with JPub and no any problems has occupied before. But now I intend for build EJB that use JPub produced classes, and the main problem is the JPub produced classes not serializable. Of course I try to subclass those classes and implements on them java.io.Selializable on both oracle.sql.Datum and java.sql.SQLData but marshaling error still present.
My question is: if I pass to the client from EJB instance any object, this object must be one of the following class: String, BigDecimal, or user defined class contains only Selializable field? And I cannot use objects passed by value with classes like oracle.jpub.runtime.MutableStruct or java.sql.Array? If yes, that is mean JPub not useful tool for EJB development, and I must provide my own classes for my Oracle Objects that implements java.io.Serializable with only Serializable fields?
null

Bug in Java objects not serializable

I plan to use the latest version TopLink 10.1.3.1.0 with Oracle Database 10g (10.2.x).
Do I still have to use the “Type Conversion” mapping as I had to do in order to address the reported non-serializable bug exiting in TopLink (9.0.4.5). See the link for the bug description:
http://www.oracle.com/technology/documentation/1012_solaris/relnotes.1012/relnotes/toplink.htm#CEGEBDEG
My Java object instance variable is defined as java.sql.Timestamp and the corresponding data type on the Oracle DB is defined as TIMESTAMP(6). Can I use the direct-to-field mapping from now on with new TopLink 10.1.3.1.0 without the serializable issue? If I still have to use the Type Conversion mapping, please help provide some detail about the mapping.
Many thanks for any help.

From what I can understand from your reply, I can use the direct-to-field mapping for Java class attribute of java.sql.Timestamp to the Oracle DB 10.2.x data type of TIMESTAMP(6) without any issue of not serializable. Please confirm. Many thanks!
By the way, I am having the same issue (Java objects not serializable) with Oracle DB 10.1.x when I use the direct-to-field mapping. It seems to me that this is more than the Oracle 9i JDBC driver.
If I have to do this with TopLink 10.1.3.1.0 + Oracle 10.2.x, I plan to use the Type Conversion with:
Java class attribute: java.sql.Timestamp
DB data type: oracle.sql.TIMESTAMP
Is this the proper way to do it? Please confirm.

Acrobat X with CS6 Suites

Ok I understand that Acrobat X is not supported directly with the AAMEE tool.
All the documentation states that you can use the Acrobat customization tool if needed, just so long as you don't serialize with it (makes sense, it should use the CS Suite serial and licensing). Though they also mention to use the same serial as the CS suite in some docs.
My question is can I use the same package+commandline for Adobe Acrobat X, that AAMEE produced when I built a package for say Design Standard Suite, with the other CS suites?
From what I understand, Acrobat X does not have a serial on its own (I also don't see the CS suite serial in any of the XMLs or msi code). Once it installs (or first run after CS install) it find the suite code and activates itself.
If my assumption is correct, in theory it would use what-ever serial code the installed CS suite used... and that I could use the same acrobat install for ALL the CS suites, rather then build a acrobat x install for each suite indivitually...
Thoughts?

Thanks for the input on that Dandirkmn. We may look at changing the prominence. So far most of the posts in the Creative Suite Enterprise Deployment forum though have been very much on topic. But increasing the capability of discovery might be useful if I see a high number related posts in the Download, Installation, and Setting up Forum.

Difference between Serialization Vs Externalization

hi can anyone tell me Difference between Serialization Vs Externalization

Serialization is the process of converting an object into a sequence of bits so that it can be persisted on a storage medium (such as a file, or a memory buffer) or transmitted across a network connection link. This process of serializing an object is also called deflating or marshalling an object.
The serialization mechanism has been added into the Java language for two reasons:
(1) the JavaBeans mechanism uses serialization.
(2) remote method invocation (RMI) allows you to automatically use objects located at another host in the network just like any local objects.
In order to serialize an object, you need the output stream OutputStream, which must be put into the special serialization stream called ObjectOutputStream. After that, you only need to call the method writeObject() to serialize the object and send it to the output stream. . Classes ObjectInputStream and ObjectOutputStream, which respectively implement the ObjectInput and ObjectOutput interfaces, enable entire objects to be read from or written to a stream (possibly a file). To use serialization with files, we initialize ObjectInputStream and ObjectOutputStream objects with stream objects that read from and write to files—objects of classes FileInputStream and FileOutputStream, respectively
Vinayworld class implements serializable interface.
Other class would be
In this code object of the vinayworld class is serialized into a file name vinay.txt
Serialization is a Marker interface -Marker Interface is used by java runtime engine (JVM) to identify the class for special processing.
Use serialization when you need to add data to the serialization stream that is not an object data member.
Externalization is same as Sterilization except that WriteObject() and ReadObject() method are called by JVM during sterilization an desterilization of object. One thing you can do with Externalization is that you can store extra information into object like STATIC variables and transient variables or you can add more information if you have any business need. One good example is compressing and uncompressing of data to send it through network or converting one format to other like a BMP image to JPEG or GIF format.
Externalization allows you to customize how serialization is done. By implementing externalization you are controlling what gets serialized ( and what doesnot ) as versus default serialization where all non-transient attributes get serialized.
For “fat data” classes with a large number of attributes only a few of which needs to persisted, externalization will help you reduce the size of serialized stream and the time taken to serialize the object. But there will be an overhead involved because the runtime has to call your methods to read/write objects.
Read more: http://www.techartifact.com/blogs/2009/06/serialization-vs-externalization.html#ixzz2mWAYCMRz

Serialization in XI

I have got 4 interfaces..........
3 are RFC-jdbc scenarios and 4th is JDBC to RFC scenario....
consider A,B, C, D are the scenarios.
But these are dependent . First A interface, then B, and C. This is the order where the interfaces should execute.
1.How to do that

hi,
1. in your case it's not a problem of how to design your interfaces
but about the adapters you use
RFC adapters for example (both sender and receiver) cannot be used
in serialized mode (qRFC) so actually you can never make them
go exactly once in order in standard (as when one RFC fails
the second one will get executed immediately not waiting for the first one
to restart)
what you can do to minimize the effect is to use
one jdbc and one RFC that will cover first three scenarios (a,b,c)
this way they will be executed exactly as you need
and then just do the D scenarion RFC - jdbc
2. what Pradeep said about serialization with a BPM would be impossible to achive as per my explanations
Regards,
Michal Krawczyk
http://mypigenie.com - XI/PI FAQ

Re-serialization of Adobe CS6

We've serialized Adobe CS6 Design & Web Premium with AAMEE 3.0's serialization file. If we wanted to re-serialize with a different serial number or change the Adobe ID or both, would you create a new serialization file with the new details and run that (so that the previous serialization info would be overwritten), or would you need to unserialize first?

It seems that when you create a new serialization file and run that it will overwrite the old one. So easiest way is to do it is to create a new one and then run it.

Can I use beancontext with XMLDecoder?

I have a bean compositing application that can build a graph of beans, some beancontext-aware, some not (e.g. Swing components). I currently serialize this, and restore and "run" the graph in a runtime application. I extend ObjectInputStream.resolveObject() to add the context-aware beans to the runtime BeanContext.
I would like to replace the serialization with the new long term persistence for beans (XMLEncoder/XMLDecoder). However, I cannot figger out how to get the context-aware beans into the BeanContext when the lot of them are restored from XML, because XMLDecoder isn't extensible like ObjectInputStream is.
How is this supposed to work?

Thanks! I had seen the owner property, but had not understood it. Looks like it will work. However, you immediately find a bug in the JDK's built-in PersistenceDelegate for BeanContextSupport. It isn't too hard to replace it with your own (I submitted a bug on this).
Do you think anyone actually uses the beancontext package? No one ever writes about it. And this is a pretty obvious bug.
--kerry.

Serialization with 6.0

Similar Messages

Maybe you are looking for