By using our site, you acknowledge that you have read and understand our Cookie Policy , Privacy Policy , and our Terms of Service. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. I have a class that extends from Printable, it prints fine using the standard PrintJob, but i would like to move to DocPrintJob so i can listen to the status of the print successful print etc. So now my code became this. I am not sure if it is because maybe i have not set the paper size, like i did when i was using PrintJob?

Author:Mazugar Nikorn
Language:English (Spanish)
Published (Last):22 October 2012
PDF File Size:2.94 Mb
ePub File Size:5.22 Mb
Price:Free* [*Free Regsitration Required]

Print service implementors should close any print data streams ie Reader or InputStream implementations that they obtain from the client doc.

Robust clients may still wish to verify this. An exception is always generated if a DocFlavor cannot be printed. Parameters: doc - The document to be printed. If must be a flavor supported by this PrintJob. If this parameter is null then the default attributes are used. Throws: PrintException - The exception additionally may implement an interface that more precisely describes the cause of the exception FlavorException.

If the document has a flavor not supported by this print job. If one or more of the attributes are not valid for this print job. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.

All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy. An object implementing this interface is obtained from a print service. Determines the PrintService object to which this print job object is bound. Obtains this Print Job's set of printing attributes. The returned attribute set object is unmodifiable. The returned attribute set object is a "snapshot" of this Print Job's attribute set at the time of the getAttributes method call; that is, the returned attribute set's object's contents will not be updated if this Print Job's attribute set's contents change in the future.

To detect changes in attribute values, call getAttributes again and compare the new attribute set to the previous attribute set; alternatively, register a listener for print job events. The returned value may be an empty set but should not be null. Registers a listener for event occurring during this print job. If listener is null, no exception is thrown and no action is performed.

If listener is already registered, it will be registered again. Removes a listener from this print job. This method performs no function, nor does it throw an exception, if the listener specified by the argument was not previously added to this component. If a listener was registered more than once only one of the registrations will be removed.

Registers a listener for changes in the specified attributes. To determine the attribute updates that may be reported by this job, a client can call getAttributes and identify the subset that are interesting and likely to be reported to the listener. Clients expecting to be updated about changes in a specific job attribute should verify it is in that set, but updates about an attribute will be made only if it changes and this is detected by the job.

Also updates may be subject to batching by the job. To minimise overhead in print job processing it is recommended to listen on only that subset of attributes which are likely to change. If the specified set is empty no attribute updates will be reported to the listener.

If the attribute set is null, then this means to listen on all dynamic attributes that the job supports. This may result in no update notifications if a job can not report any attribute updates. Removes an attribute listener from this print job. If the listener is null, no exception is thrown and no action is performed. If a listener is registered more than once, even for a different set of attributes, no guarantee is made which listener is removed.

Prints a document with the specified job attributes. This method should only be called once for a given print job. Calling it again will not result in a new job being spooled to the printer. The service implementation will define policy for service interruption and recovery. When the print method returns, printing may not yet have completed as printing may happen asynchronously, perhaps in a different thread.

Application clients which want to monitor the success or failure should register a PrintJobListener.


Subscribe to RSS



Java example source code file (



Java Examples for javax.print.DocPrintJob




Related Articles