Probably not. At least not in any useful way.
One of the main reason sequence diagrams are useful is that they can describe asynchronous activities in a generally deterministic manner.
For example, let's say we have an object (it could be a
servlet, a message-driven bean, a web-service listener, a UI component, or whatever). The code instantiates this object and links it to some form of input so that a message will be called when something happens. All that the code (and thus a reverse engineering tool) can
possibly express is that this method might be called, zero or more times, some time in the future.
A well-crafted sequence diagram, on the other hand, can xepress domain information such as the events, situations and scenarios which will trigger this method to be called, including when and how often it should be called in the real system.
This type of "callback" behaviour is
very common in
Java systems.
