Choicebox with Domain-Objects
Hi,
I'm struggeling to find out how to deal with ChoiceBox and domain objects whose toString-method is not appropriate for the label. For ListView I'm able to set a cell factory where I was able to customize the domain to string translation but I'm unable to find something similar for ChoiceBox.
Tom
Guess what I've done [1] ;-)
[1]https://github.com/tomsontom/emfdatabinding-tutorial/blob/master/org.eclipse.ufacekit.ui.jfx.databinding/src/org/eclipse/ufacekit/ui/jfx/databinding/controls/ChoiceBoxViewer.java
Similar Messages
-
Domain Object and Service oriented pattern
We have J2EE based application with following components, we are facing some issues with existing system.
Current System : We have J2EE based application. The following is the flow.
Client Layer [including JSP, Struts ] action classes  Delegates  Session fa�ade [Session bean]  DAO EJBDAO  EJB. We use CMP, xDoclets , JBOSS.
1. Our Domain objects are heavy. I know they are suppose to be coarse objects but they take more time in loading. Also, we noticed one thing that lot of methods are called during Domain Object creation process and it takes lot of time in loading. Actually, we dont really know what is happening as we are using CMPs.
Question :
- Any input on what can be done to avoid Domain object excessive loading time.
- Anyone can share there experiences with Domain objects. Are you facing issues related with performance.
- We dont use DTO, we pass domain objects between. Do you see any problem in doing that.
2. Currently, our system was used by one single front end or lets say we have only one client but soon we will have more clients using it.
Question :
- What should be our design approach. How can we make our system more like service oriented. If the two clients demand different business logic then how it will be handled. Business logic common to all the clients will be handled by which layer and business logic specific to client will be handles by which layer.
- Please suggest based on our existing infrastructure. We don�t want to use SOAP or cannot make drastic changes to our flow.
We have domain and services in the same package and we are doing the refactoring of code, your inputs will be valuable.
Thanks
SandipanWhat type of logger do you use and what is the loger-level during production?
If it is log4j set the logger to level INFO or WARN.
This might sound trivia but can make a difference between 20seconds and 500 ms. -
Issue when SelectOneChoice is used with Domain data type in JDev 11.1.2.0.0
Hi,
I am facing one issue while working with SelectOneChoice along with Custom Domain data type. Sample app to simulate the issue is available at http://www.filejumbo.com/Download/6FDF6ECF2922BD24
Issue Details.
Base view object’s attribute is of type CustomString, for which another static VO’s attribute is attached as LOV. LOV attribute is of type String. Because of this data type mismatch between LOV VO attribute and Base VO attribute, while working in screen, initially we were facing Class cast exception.
Cannot convert <<LOV Attr. Val.>> of type class java.lang.String to class model.domain.common.CustomString This is not only for this type of SelectOneChoice but also for InputText field whose underlying VO attribute is of type CustomString (i.e. any Custom Domain type)
On raising this in Jdeveloper forum, I came to know that adding a default oracle converter against the UI Component will take care of converting to respective data type. After added the converter for InputText and SelectOneChoice components, this issue got resolved. This was our lesson while working in Jdeveloper version 11.1.1.3.0. Converter we used,
<f:converter converterId="oracle.genericDomain"/> When we try the same scenario in Jdev Version 11.1.1.4.0, without having the oracle converter itself, SelectOneChoice started working fine!! (i.e. it is able to set the base attribute with LOV attribute’s value but with proper base attribute’s domain data type). Anyhow, converter is required for InputText.
When we try the same scenario in Jdeveloper new version 11.1.2.0.0, it started giving class cast exception when we don’t have oracle converter for SelectOneChoice. But by adding it, though it didn’t give such class cast exception message, though a selection is made in SelectOneChoice, VO attribute has not been updated with the new value. Instead it is updated with null value (Checked the setter method of view row impl by having break point) . Because of this, after a selection is made, when we try to read the attribute value from VO on button click, VO attribute always returns null.
We have also tried our own converters but there is no change in the behavior.
The above misbehavior can be tested either by having SOP programmatically or by refreshing the SelectOneChoice by giving its id as Partial trigger to itself with autosubmit set to true, so that the selected value will be reset to null irrespective of the selection made.
For convenience, Issue details with Sample application is shared. Shared link : http://www.filejumbo.com/Download/6FDF6ECF2922BD24
Shared folder contains
1. Sample App developed on Jdev 11.1.1.4.0 to ensure it didn’t give this error.
2. Sample App developed on Jdev 11.1.2.0.0 to simulate this error.
3. Error details in a document.
Can anybody have a look at this and tell me why this misbehavior and is it a bug? If so, any workaround available to continue the development?
Thanks in Advance.
Raghu
Edited by: Raguraman on Sep 10, 2011 10:31 AMSorry for the late reply John and Frank. Ya i did. Thank you.
One more detail:
I tested the behavior in Jdeveloper 11.1.2.0.0. The recent surprise is Select One Choice is behaving perfectly when it used in Grid layout and fail to work when it is form layout. I am getting surprised why behavior of component varies based on the way it refers the binding.
for form layout,
value=#{bindings.
for grid layout,
value=#{row.bindings.
The bug details (#/title) are Bug 12968871 - RUNTIME CONVERSION FAILURE WHEN USING CUSTOM DOMAIN OBJECT VALIDATION IN EO
Edited by: Raguraman on Sep 12, 2011 8:23 PM
Edited by: Raguraman on Sep 12, 2011 8:31 PM -
Using domain object instead of generated ones?
I'm using NetBeans, and I'm curious if there's a way that we can use our domain objects with the web service calls rather than the empty stubs generated by wsgen?
wsgen creates the skeletal client classes, as well as an ObjectFactory that returns instances of those classes. I imagine I could modify ObjectFactory to return our domain objects instead, but then we'd be breaking with wsgen.
Is there a better solution to this?
Thanx!You can associate a Virtual Host to the loopback IP address 127.0.0.1 read about Virtual Hosts here: http://tomcat.apache.org/tomcat-6.0-doc/virtual-hosting-howto.html
But with the above configuration alone you can access your app via http://somedomainname.com only on your local machine, no one else on the internet will see it. -
hi,
Normally when i want to persist a domain object like Customer object to a database, my statements will be below,
// code from my facade
Customer cust = new Customer();
cust.setFirstName("myname");
cust.setLastName("mylastname");
// set another attributes
cust.create();
with this code i have a CustomerPersistence object to handler for create this customer record to a database. Now j2ee have a DAO pattern. So my question is,
1.where is a domain object within DAO pattern? --> because of we can reused domain object.
2.DTO is Domain Object, isn't it?
3.when i look at some articles about DAO, many of it will present in this way
facade -->create DTO --> call DAO (plus something about factory pattern)
i never see something like this
facade --> domain object --> dao
any suggestion?
anurakth
sorry for my english!!Hi,
I am a bit confused about implementation of the domain model and I wondered if you could help. My main concern is that I am introducing too many layers and data holders into the mix. Here is what I am thinking.
DTO - used to carry data between the presentation and the services layer
Service Class - coordinates the calling of domain objects
Domain Object - models a domain entity, service layer logic specific to this object is to be implemented here.
Data Object - an exact representation of a database table. many to many relationship between domain object and data object.
Hibernate DAO Class - has no properties, just methods used for read and writing the object to the database. It is passed in the Data Object for persistence. Is it wrong that the DAO contains no properties?
Perhaps the domain object will contain each data object it is comprised of. I was originally going to keep calls to DAOs in the Services class (as recommended in http://jroller.com/page/egervari/20050109#how_to_change_services_logic ) but I am thinking that each domain object could expose a save method, and that method would co-ordinate persisting itself to the various tables it is derived from.
Does this sound resonable? I have trouble finding a pattern on the net that clealy defines the Domain Model. I was tempted to map Domain Objects directly to database tables, and simply persist the Domain Object, but this 1-1 relationship may not always hold true.
Thanks. -
Get the pc name with domain name and add it to my properties file using commands
i want to get the pc name with domain name and add it to my properties file using powershell .
sidfunction Get-Environment{
[environment]|Get-Member -Static -MemberType Properties |
ForEach-Object{
if($_.Name -ne 'StackTrace'){
$v=[scriptblock]::Create("[environment]::$($_.Name)").Invoke()
New-Object PsCustomObject -Property ([ordered]@{Name=$_.Name;Value=$v[0]})
Get-Environment
Get-Environment | Out-String | Out-File environment.txt
¯\_(ツ)_/¯ -
Hello,
I'm working with an application where we have many, many, many domain objects that could be added to a "header". In my business/service interface I don't like to write 50+ of addX(...), addY(...), addZ(...) etc. methods.
Every domain object extends a domain object base class. In my business/service interface I've added one single method for adding domain objects to make the interface somewhat smaller:
public void add(DomainObject[] someDomainObjects);
...The elements of the domain object array are of different kind, but all extends the domain object base class. I'd like to implement class and method that have a strategy for determining what kind of domain object the current one is in the given array and invoke the correct add(...) method for that particular domain object.
The most simple way of doing it is to have a very big if-else using instanceof to determine what kind of domain object it is, but it doesn't feel like a very nice design.
Example:
public class MyBusinessObject {
public void add(DomainObject[] someDomainObjects) {
// Iterate over all domain objects in the array
for (DomainObject domainObject : someDomainObjects) {
// Determine what kind of domain object it is and create the correct DAO
if (domainObject instanceof X) {
DomainObjectXDao xDao = new DomainObjectXDao();
// Save the current domain object
xDao.save((X) domainObject);
} else if (domainObject instanceof Y) {
DomainObjectYDao yDao = new DomainObjectYDao();
// Save the current domain object
yDao.save((Y) domainObject);
} else if (domainObject instanceof Z) {
DomainObjectZDao zDao = new DomainObjectZDao();
// Save the current domain object
zDao.save((Z) domainObject);
} else if (...) {
}Is there any design pattern for making this a more nice design?
If anyone could contribute with their good knowledge I'd be very glad!
Regards, Andreas ErikssonMap the DomainObject types to their respective DAOs and look them up as you loop through them in the add method, e.g.:
public class MyBusinessObject {
private Map daos = new HashMap();
daos.put(X.class, new XDomainTypeDAO());
daos.put(Y.class, new YDomainTypeDAO());
daos.put(Z.class, new ZDomainTypeDAO());
public void add(DomainObject[] objs) {
for (DomainObject obj : objs) {
Class type = obj.getClass();
DAO dao = (DAO) daos.get(type);
if (dao == null) {
throw new IllegalArgumentException(
"No DAO configured for DomainObject type " + type);
dao.save((DomainObject) obj);
}You'd have to create a DAO interface (or abstract base class) which defines a save method with the signature public void save(DomainObject obj). Then each DAO would have to implement this method and cast the passed domain object to the expected type.
To take things further, you could introduce a DAOProvider interface to hide where the MyBusinessObject obtains the DAOs from (rather than have it maintain the map), e.g.:
public interface DAOProvider {
DAO daoFor(Class domainType);
// A really simple implementation - assmes that DAOs are thread-safe
public class SimpleDAOProvider implements DAOProvider {
private Map daos = new HashMap();
daos.put(X.class, new XDomainTypeDAO());
daos.put(Y.class, new YDomainTypeDAO());
daos.put(Z.class, new ZDomainTypeDAO());
public DAO daoFor(Class domainType) {
DAO dao = (DAO) daos.get(type);
if (dao == null) {
throw new IllegalArgumentException(
"No DAO configured for DomainObject type " + domainType);
return dao;
}The advantage of this is you can alter the strategy for handing out DAOs, e.g. pass the same instance back each time, or dynamically instantiate a new instance, etc. Of course, you need a way for the MyBusinessObject to get hold of a DAOProvider instance (inject it? Have it use a factory?) -
I checked dozens of internet pages but didn't find an answer on that question.
Domain is everything meaningful in the scope of
current task, thus domain object is an abstraction of
the real or imaginable entity from the scope of
current task.Can you please give me an example?
I will now explain a little bit why I am asking. But please don't forget to give me an example.
We use the root object as a domain object. "Article" is a domain object in our company. An Article has a 1:m relationship with a "PackageUnit". The PackageUnit is no domain object. Furthermore the PackageUnit has a 1:m relationship with SalesHistoryWeek (which is no domain object too) and so on.
Only the domain object (Article) can create new instances of the objects which are linked to it (PackageUnit and so on). A PackageUnit cannot create a new instance of SalesHistoryWeek, only Article can do this, the domain object.
Furthermore only the domain object has getter and setter methods for the linked non domain objects. So the domain object "jumps" over many knots to get or set an object.
I think this is a strange design and so I am asking here for the meaning of domain objects. Besides this, the coupling of objects is very large in my example and it doesn't respect the Law of Demeter.
What do you think? -
Strange problem with Domain Values
Dear All,
I encounter one strange problem with Domain Fixed Values.
Background:
We have a custom domain ( ZXREF2) created for custom data element(ZXREF2) which has replaced standard dataelement in BSEG for field XREF2. This domain has 12 Fixed values. The idea was to have F4 help for field "Reference Key2" in FBL5N/FBL01 tcodes. It is working fine with these 12 Fixed value, means, on F4 we could see all these 12 values and when selecting a line from F4 the entry got thru the screen validation ( plz note hat this validation is like checking the mandatory value so this is done even before PAI).
Problem:
The requirement was to add a new line to F4 values( tecnically, 13th record in domain ZXREF2). We added this line to domain and moved to Quality system. Its working fine in both Dev and Qality, but the strange problem occured after moving and testing in Production.
In production, we could see all 13 lines in F4 help. <b>BUT</b>, after selecting the new one( 13th one), and after the value appears on screen field, when Enter is pressed, it gives error message "Enter Valid value".
This error message also comes when we enter any value which is not there in F4. That means, system is able to recognize the new value in F4, but falied to validate that.
We thought that, this might be the problem with Buffer, and request Client to re-start the system. Even after system restart, it still gives the same error message.
Please note that, the error message is triggered even before PAI of the screen called. So noway( I already tried system debugging) we can debug this error message to findout the rootcause.
Any quick help would be highly appriciated.
Thanks and Regards,
Prasad.Hello Max,
I guess DB Utility ( SE14 ) is to be run only when there is a change at structure level, to make Runtime and Database objects in sync. Here, we just added a new line to existing domain, and this added a new row to the Database table DD07T/DD07L.
Could you please expalin it more clearly if your view is different that what I just described.
Prasad. -
Where to put logic with Transfer Objects?
I'm playing with Transfer Objects for the first time, and have got this one class I'm not sure how to design the Transfer Object for. The problem is that I have some logic that is needed by both the domain model and by the client.
The class is named Moment. It's basically a wrapper around the java.util.Calendar class because I don't like passing objects of that type around in my code. That Calendar class is just to complicated to expose everywhere.
So, an easy example is that internally, Moment stores time in millitary time. I need a method that will take an hour, a minute, and AM or PM and convert it to millitary time for storing internally in the Moment.
Before Transfer Objects, this was easy enough of a decision. Moment had several factory methods called makeMoment. One of these took three arguments: hour, minute, and AM or PM. And, it internally converted to millitary time and stored the time in the Moment. However, now that the client is operating on Transfer Objects and not Domain Objects, if I put that method on Moment in the domain model, it won't be available to the client. If the client takes user input in AM/PM format from the user, it would have to duplicate logic already implemented in the model.
Options I think I have:
1.) Put the conversion method in MomentTO, maybe make it static. Then, my Moment class calls this method on MomentTO to do the coversion. This would work, but it seems funny to have the domain model calling business logic inside the Transfer objects.
A variation of this solution is just whenever my domain model wants to create a Moment, have it first create a MomentTO via a factory method that could do the coversion, and pass the MomentTO to a Moment constructor. This seems even funnier though to have the domain model creating Transfer Objects for internal use. It just seems to me that the point of Transfer Objects is to export information about the domain model to the client, leaving a lot of the specifics behind. Not something that the domain model uses for processing internally.
I could put the conversion method on the MomentTO and just say anybody who wants to create a Moment using anything but millitary time is going to come from the client that will be using Transfer Objects. Nobody else will be creating moments using anything but straight millitary time. But, this approach seems inflexible.
2.) Make a separate library / package that is available to both the domain model and the client. The inital reason I don't like this solution include the fact that I don't need much more other logic to be shared like this, so this package would be really, really small.
Any suggestions? Just can't seem to find something that makes good sense. I do have several other things like this for this Moment class in creating a Transfer Object for it. But, it is just this one class that I'm having this problem with.>>
If this is for the pursuit of knowledge, then thatis
all well and good. However, if you actually wantto
do something with this application, I wouldrecommend
the following link:
http://xp.c2.com/YouArentGonnaNeedIt.html
- SaishI think you missed the part in the thread where I'm
not seeing the evil of Transfer Objects. Please
explain. They really don't seem that much work to
develop to me.
Fair enough. However, my point is that any time you develop something that 'might' be needed is time you are taking away from time developing things that 'are' needed.
One of the listed advantages of the Transfer Object
pattern in the Core J2EE Patterns is hiding
complexities of the domain model from the client.
This seems to be very handy for my application.The session facade pattern would accomplish the same effect.
. Many of the domain model objects are versioned,
but the first three iterations of development that I
want to complete before deployment need to know
nothing about the versions. With transfer objects,
this can all be safely hidden in the Application
Service objects.
I fail to see how transfer objects themselves would not require versioning or modification. Given a large enough transfer in the domain model, it woud be difficult to insulate an associated transfer object. Granted, these changes may occur less frequently.
Plus, I'm trying to figure out how the hell Commons
Validator works with Spring. Really wish I could
find a getting started guide. What I've found so far
makes it look like it's going to be easier to
validate Transfer objects than my domain model
objects, because all the validated fields will be on
one object. Not mostly on one object with some
fields scattered about like they would be with domain
model objects...I've found good FAQ and HOW-TO documentation at Jakarta while working on several Commons projects, including Log4J and FileUpload. Validator has no such online documentation?
For Spring, I recommend the new Johnson "J2EE Development with Spring" and (I forget the author) "Spring in Action".
- Saish -
How to bind Hibernate domain objects to the UI layer
Dear All,
I am trying to bind FX UI controls to properties of a Hibernate Domain object. Is there any good example to refer to for this purpose?
Thanks & Regards,
Nitin GuptaAssuming you do not formulate your hibernate objects as pojos with javafx properties directly, if the hibernate object is a pojo with or without PCL, you can convert the properties of the pojo to observable values (or properties) directly. These are used in a bind statement.
Check out what jgoodies does with BeanAdapter or PresentationModel. You need the same concept. I've attached a class that does this for a pojo already (its an incomplete port of jgoodies PresentationModel). It will work for any pojo. It does not have setter support as it was just a demonstration. Its efficient for a pojo with a large number of properties. You could also write a very short property connector to produce one observable value per property. The value of the class below is to be able to swap out the bean being observed without having to change or reset the property observable values each time. Bind once and then just reset the bean (think master detail).
package scenegraphdemo;
import java.beans.PropertyChangeEvent;
import java.beans.PropertyChangeListener;
import java.lang.reflect.Method;
import java.util.HashMap;
import java.util.Map;
import javafx.beans.property.ObjectProperty;
import javafx.beans.property.ObjectPropertyBase;
import javafx.beans.property.Property;
import javafx.beans.property.StringProperty;
import javafx.beans.value.ChangeListener;
import javafx.beans.value.ObservableValue;
import javafx.beans.value.WritableValue;
* An object binding object that creates object bindings based on property names
* specified as strings. This is a convenience class to avoid having observable
* values directly dependent on the underlying bean. The actual bean the
* properties connect can be changed dynamically using the channel or
* <code>setBean</code>. This allows you to setup binding when you don't have
* the bean to bind to or the bean to bind to will change as in the detail part
* of a master-detail screen. Generally, the return values from
* <code>getProperty()</code> should be used for binding not the factory itself.
* The object should be a domain object bean with bean methods to get or set the
* value using java bean naming conventions OR it should use javafx property
* definition conventions. The factory will automatically listen for standard
* java bean changes using <code>PropertyChangeListener</code> approaches unless
* you indicate to not to.
* <p>
* When the bean itself changes, the properties fire to indicate that their
* values may have changed and the observing object should update itself. This
* object allows you to integrate your javafx/POJOs into the binding
* infrastructure without being dependent on the actual underlying bean. If you
* are familiar with jgoodies <code>BindingAdapter</code> this is a similar
* class.
* <p>
* This only handles reading bean properties. Need to add set() logic.
* <p>
* TODO: Make this work better. Many corner cases to cover.
* <p>
* TODO: Instead of just method calls on POJOs, also check for PCL. Note that
* javafx properties won't work easily they are always tied to the underlying
* object so I would have to write another CaptiveObjectProperty object that is
* essentially a delegator.
public class BeanPropertyFactory<T> extends ObjectProperty<T> {
ObservableValue<T> channel;
Map<String, CaptiveObjectProperty> properties = new HashMap<String, CaptiveObjectProperty>();
boolean listenForBeanPCLEvents = true;
public boolean isListenForBeanPCLEvents() {
return listenForBeanPCLEvents;
public void setListenForBeanPCLEvents(boolean listenForBeanPCLEvents) {
this.listenForBeanPCLEvents = listenForBeanPCLEvents;
if (getBean() != null)
removeBeanPCLListener(getBean());
* The bean channel where the bean is obtained.
* @return
public ObservableValue<T> getChannel() {
return channel;
public BeanPropertyFactory() {
setChannel(new ObjectProperty());
public BeanPropertyFactory(ObservableValue<T> channel) {
if (channel == null)
setChannel(new ObjectProperty());
else
setChannel(channel);
protected void setChannel(ObservableValue<T> channel) {
if (this.channel != null) {
removeBeanChangeListener(this.channel);
this.channel = channel;
if (this.channel != null) {
addBeanChangeListener(this.channel);
updateStringProperty(getBean());
invalidateProperties();
fireValueChangedEvent();
protected StringProperty stringProperty = new StringProperty();
* The string property is an observable toString property. It cannot be set.
* @return
public StringProperty beanStringProperty() {
return stringProperty;
public String getBeanString() {
return beanStringProperty().getValue();
* A listener that listens to changes in the bean channel. This only fires
* when the bean changes not when the properties on the bean change. The
* default actions updates the "string" property representation of this
* object as well as attaches property change listeners.
* @author Mr. Java
protected class BeanChangeListener implements ChangeListener {
@Override
public void changed(ObservableValue arg0, Object arg1, Object arg2) {
if (arg1 != null) {
BeanPropertyFactory.this.removeBeanPCLListener(arg1);
if (arg2 != null) {
BeanPropertyFactory.this.addBeanPCLListener(arg2);
updateStringProperty(arg2);
protected void updateStringProperty(Object obj) {
if (obj != null)
beanStringProperty().setValue(obj.toString());
else
beanStringProperty().setValue("null");
protected void removeBeanChangeListener(ObservableValue<T> obj) {
if (beanChangeListener == null)
beanChangeListener = createBeanChangeListener();
if (obj != null) {
obj.addListener(beanChangeListener);
protected void addBeanChangeListener(ObservableValue<T> obj) {
if (beanChangeListener == null)
beanChangeListener = createBeanChangeListener();
if (obj != null)
obj.removeListener(beanChangeListener);
* The instance of a change listener for detecting when the bean in the bean
* channel changes.
ChangeListener beanChangeListener = new BeanChangeListener();
* Subclass can override to create their bean change listener.
* @return
protected ChangeListener createBeanChangeListener() {
return new BeanChangeListener();
public BeanPropertyFactory(T bean) {
setChannel(new ObjectProperty(bean));
public Property getProperty(String property) {
if (property == null || property.isEmpty())
throw new IllegalArgumentException("Property cannot be null");
if (properties.containsKey(property))
return properties.get(property);
CaptiveObjectProperty p = new CaptiveObjectProperty(this, property);
properties.put(property, p);
return p;
@Override
public T getValue() {
return getBean();
* A listener that listens for property change events on the bean. When the
* bean changes, the listener must be removed then attached to the new bean
* but can use the same instance of this class. The action is to inform any
* existing property objects that the property has changed. The detection of
* property changes is centralized in the factory class for efficiency.
protected class BeanPropertyListener implements PropertyChangeListener {
@Override
public void propertyChange(PropertyChangeEvent evt) {
if (properties.containsKey(evt.getPropertyName())) {
CaptiveObjectProperty p = properties.get(evt.getPropertyName());
p.propertyChanged();
updateStringProperty(getBean());
* The cached listener instance to listen to the bean (in the bean channel)
* property change events if it supports PCL.
PropertyChangeListener beanPropertyListener;
* Subclasses can override to implement their own behavior. Its best to
* extend from <code>BeanPropertyListiner</code> to include the default
* behavior.
* @return
protected PropertyChangeListener createBeanPropertyListener() {
return new BeanPropertyListener();
* Add a listener only if the PCL methods exist. This listens for property
* changes on the bean's property not changes in the actually bean held by
* the bean channel.
protected void addBeanPCLListener(Object obj) {
if (!isListenForBeanPCLEvents())
return;
if (obj != null) {
if (BeanPropertyUtils.hasPCL(obj.getClass())) {
if (beanPropertyListener == null)
beanPropertyListener = createBeanPropertyListener();
BeanPropertyUtils.addPCL(obj, beanPropertyListener, null);
* Remove a listener only if the PCL methods exist.
* @see #attachBeanPCLListener
protected void removeBeanPCLListener(Object obj) {
if (obj != null) {
if (BeanPropertyUtils.hasPCL(obj.getClass())) {
if (beanPropertyListener == null)
beanPropertyListener = createBeanPropertyListener();
BeanPropertyUtils.removePCL(obj, beanPropertyListener, null);
* Invalidate the properties in the property cache. Then changed the bean in
* the bean channel. Then fire a value changed event.
* @param bean
public void setBean(T bean) {
invalidateProperties();
if (getChannel() instanceof WritableValue) {
((WritableValue) getChannel()).setValue(bean);
} else {
throw new IllegalArgumentException(
"Could not set bean value into a non-writable bean channel");
fireValueChangedEvent();
* Called to indicate that the underlying bean changed.
protected void invalidateProperties() {
for (CaptiveObjectProperty p : properties.values()) {
p.invalidate();
public T getBean() {
return getChannel().getValue();
* Lazily get the method representing the property prior to getting or
* setting. Because this is a property, it can also be bound to.
* @author Mr. Java
* @param <T>
protected static class CaptiveObjectProperty<T> extends
ObjectPropertyBase<T> {
* The string name of the property.
String readPropertyName, writePropertyName;
* If the property is really a javafx property, it is stored here.
Property<T> enhancedProperty;
* Used if the property is not an enhanced property.
Method readMethod, writeMethod;
* The factory that holds the bean we obtain values against.
BeanPropertyFactory factory;
public CaptiveObjectProperty(BeanPropertyFactory factory,
String property) {
this.readPropertyName = property;
this.factory = factory;
public CaptiveObjectProperty(BeanPropertyFactory factory,
String property, String writePropertyName) {
this.readPropertyName = property;
this.writePropertyName = writePropertyName;
this.factory = factory;
@Override
public Object getBean() {
if (factory == null || factory.getBean() == null)
return null;
return factory.getBean();
@Override
public void store(T value) {
if (writeMethod == null && enhancedProperty == null) {
getWriteMethod(value.getClass());
if (writeMethod == null && enhancedProperty == null) {
return;
try {
if (enhancedProperty != null) {
enhancedProperty.setValue(value);
return;
if (getBean() == null)
return;
writeMethod.invoke(getBean(), value);
return;
} catch (Exception e) {
e.printStackTrace();
@Override
public T getValue() {
if (readMethod == null && enhancedProperty == null) {
getReadMethod();
if (readMethod == null && enhancedProperty == null)
return null;
try {
if (enhancedProperty != null)
return enhancedProperty.getValue();
if (factory.getBean() == null)
return null;
Object rval = readMethod.invoke(getBean());
return (T) rval;
} catch (Exception e) {
e.printStackTrace();
return null;
@Override
public String getName() {
return readPropertyName;
* Invalidate the method. Perhaps the bean changed to another object and
* we should find the method on the new object. This is called prior to
* the <code>getBean()</code> being changed.
public void invalidate() {
readMethod = null;
fireValueChangedEvent();
* This is used to externally signal that the property has changed. It
* is quite possible that this object does not detect those changes and
* hence, an external object (in all cases the BeanPropertyFactory) will
* signal when a change occurs. Property change detection is centralized
* in the factory for efficiency reasons.
public void propertyChanged() {
fireValueChangedEvent();
protected Property getJavaFXReadProperty(String propertyName) {
if (factory.getBean() == null)
return null;
String methodName = getName() + "Property";
try {
Method mtmp = factory.getBean().getClass()
.getMethod(methodName, new Class<?>[0]);
enhancedProperty = (Property) mtmp.invoke(factory.getBean(),
new Object[0]);
return enhancedProperty;
} catch (Exception e) {
// e.printStackTrace();
// silently fail here
return null;
protected void getWriteMethod(Class<?> argType) {
if (factory == null || factory.getBean() == null)
return;
if (enhancedProperty == null)
enhancedProperty = getJavaFXReadProperty(getName());
if (enhancedProperty != null)
return;
writeMethod = getPojoWriteMethod(getName(), argType);
* Sets the method, either an enhanced property or the POJO method via
* reflection.
* @return
protected void getReadMethod() {
if (factory == null || factory.getBean() == null)
return;
enhancedProperty = getJavaFXReadProperty(getName());
if (enhancedProperty != null)
return;
// Look for standard pojo method.
readMethod = getPOJOReadMethod(getName());
* Return a get method using reflection.
* @param propertyName
* @return
protected Method getPOJOReadMethod(String propertyName) {
if (factory.getBean() == null)
return null;
// Look for standard pojo method.
String methodName = getGetMethodName();
try {
Method mtmp = factory.getBean().getClass()
.getMethod(methodName, new Class<?>[0]);
return mtmp;
} catch (Exception e) {
// silently fail here
// e.printStackTrace();
return null;
protected String getGetMethodName() {
String methodName = "get"
+ Character.toUpperCase(getName().charAt(0));
if (getName().length() > 1)
methodName += getName().substring(1);
return methodName;
* Return a set method using reflection.
* @param propertyName
* @param argType
* @return
protected Method getPojoWriteMethod(String propertyName,
Class<?> argType) {
if (factory.getBean() == null)
return null;
String methodName = getSetMethodName();
try {
Method mtmp = factory.getBean().getClass()
.getMethod(methodName, argType);
return mtmp;
} catch (Exception e) {
// silently fail here
// e.printStackTrace();
return null;
protected String getSetMethodName() {
String methodName = "set"
+ Character.toUpperCase(getName().charAt(0));
if (getName().length() > 1)
methodName += getName().substring(1);
return methodName;
* Obtain a property using the binding path. The binding path should be
* simple property names separated by a dot. The bean has to specified
* because the return value is a property that can be used directly for
* binding. The first property specified in the binding path should be a
* property on the bean.
* <p>
* The difference between this and <code>Bindings.select()</code> is not
* much other that it uses the bean factory machinery and the path can be
* specified as a string. Of course, the bean can be a plain pojo.
* @param bindingPath
* @return
public static Property propertyFromBindingPath(Object bean,
String bindingPath) {
if (bindingPath == null || bindingPath.isEmpty())
return null;
BeanPropertyFactory lastFactory = null;
Property lastProperty = null;
String[] parts = bindingPath.split("\\.");
if (parts.length > 0) {
for (int i = 0; i < parts.length; i++) {
if (parts.length() <= 0 || parts[i].isEmpty()) {
throw new IllegalArgumentException("Binding path part " + i
+ " has no length");
BeanPropertyFactory newFactory;
if (i == 0)
newFactory = new BeanPropertyFactory(bean);
else
newFactory = new BeanPropertyFactory(
(WritableValue) lastProperty);
lastProperty = newFactory.getProperty(parts[i].trim());
lastFactory = newFactory;
return lastProperty;
* Alot like <code>Bindings.select</code> but also handles pojos.
* @param bean
* @param path
* @return
public static Property propertyFromBindingPath(Object bean, String... path) {
String tmp = "";
for (int i = 0; i < path.length; i++) {
tmp += path[i];
if (i <= path.length - 1)
tmp += ".";
return propertyFromBindingPath(bean, tmp);
and a supporting classpackage scenegraphdemo;
import java.beans.PropertyChangeListener;
* Static methods for manipulating PCL for standard java beans.
* @author Mr. Java
public class BeanPropertyUtils {
protected final static Class<?>[] NO_ARGS = new Class<?>[] { PropertyChangeListener.class };
protected final static Class<?>[] ARGS = new Class<?>[] { String.class,
PropertyChangeListener.class };
protected final static String pclAddMethodName = "addPropertyChangeListener";
protected final static String pclRemoveMethodName = "removePropertyChangeListener";
* Return true if the class has PCL methods. Does not check for remove.
* <p>
* addPropertyChangeListener(PropertyChangeListener)
* <p>
* addPropertyChangeListener(String, PropertyChangeListener)
* @param bean
* @return
public static boolean hasPCL(Class<?> clazz) {
try {
if (clazz.getMethod(pclAddMethodName, NO_ARGS) != null) {
return true;
} catch (Exception e) {
// silently fail
try {
if (clazz.getMethod(pclAddMethodName, ARGS) != null) {
return true;
} catch (Exception e) {
// silently fail
return false;
* Add a listener.
* @param bean
* @param listener
* @param propertyName
public static void addPCL(Object bean, PropertyChangeListener listener,
String propertyName) {
try {
if (propertyName == null) {
bean.getClass().getMethod(pclAddMethodName, NO_ARGS)
.invoke(bean, new Object[] { listener });
} else {
bean.getClass()
.getMethod(pclAddMethodName, ARGS)
.invoke(bean,
new Object[] { propertyName, listener });
} catch (Exception e) {
e.printStackTrace();
* Remove a listener.
* @param bean
* @param listener
* @param propertyName
public static void removePCL(Object bean, PropertyChangeListener listener,
String propertyName) {
try {
if (propertyName == null) {
bean.getClass().getMethod(pclRemoveMethodName, NO_ARGS)
.invoke(bean, new Object[] { listener });
} else {
bean.getClass()
.getMethod(pclRemoveMethodName, ARGS)
.invoke(bean,
new Object[] { propertyName, listener });
} catch (Exception e) {
e.printStackTrace();
-
Annotation Agnostic Domain Objects
Hi,
I would like to know how we create annotation agnostic domain objects. At present, i have to DPL annotations in my domain object for persisting in BDB. Siince, i will be sharing
the domain objects with other projects which may or may not use BDB. So I would like to have annotation agnostic domain objects.
Is there a way to do it in BDB? I know its possible to do it with Base API. But i would like to know whether its possible it in DPL itself.
In BDB forums, there were some leads to use EntityModel and AnnotationModel which are not clear to use. I would like to have more example on this, if it is possible to do it by EntityModel or AnnotationModel.
Any help on this is Highly Appreciated.
Thanks
WilliamHi William,
Just to make sure I understand your question. You basically want to have plain domain objects, non-annotated (non DPL annotated) POJOs representing the domain objects, and you want to use them with JE's DPL, without adding the DPL specific annotations to persist the objects (something similar to what you would do with Hibernate's mapping documents). Correct?
Regards,
Andrei -
Domain Object Validation Errors
I have created a Domain object for PhoneNumber validation. Several entity attributes are defined as PhoneNumber. When validation fails for a PhoneNumber, the Domain object throws a DataCreationException with a generic error message.
I would like to be able to catch this exception and throw a new DataCreationException with a more specific error message. Is this possible?
I have a page where a users enter several phone numbers -- home, work, cell, etc. It would nice if the error message they see is specific to the phone number that failed.The mData variable in your domain class holds the value of the attribute being validated. So, in your validate() method you can throw a new DataCreationException with an error message that depends on the value of mData.
The ADF Developer's Guide has an example of this - see example 36-2 in section 36.1.4.3.
Blaise -
Yoga 2 Pro - Veriface doesnt work with Domain Account
I have a Yoga 2 Pro and I can get Veirface to work fine with a local account but it will not work with a Domain Account. I can get it to where it prompts me for the Domain Account Password (as it should the 1st time) but when you enetr the proper password, it tells you ints invalid etc. I have tried changing the Domain Password but it acts like it just cant locate the account etc. Does anyone know if this is a known issue or if there is a resolution to this?
I am using Veriface 5.0.13.5261 on a Windows 8.1 Pro Operating SystemHi there, i had the same problem.
I have two accounts
1. valentia\mubi (which is domain account)
2. Mubi (which is local laptop account)
When i use register my account with veriface, it work fine with Mubi
When i use to register my account with valentia\mubi it say wrong password..
I even deleted local i.e. Mubi account but still no luck!
This is great feature, but pretty much useless if not working with domain. I have to use domain account, -
Performance issue with Business Objects Java JRC API in CRXI R2 version
A report is developed using java JRC API in CR XI release 2. When I generate the report in the designer, it took less than 5 seconds to display the results in crystal report viewer inside the designer. But in the QA environment, when I generate the same report from the application, it takes almost 1 to 1.5 minutes to display the same results in PDF. I also noticed that if the dataset contains bigger volume of data, then the reports are taking even longer almost 15 to 20 minutes.
While generating the report from the application, I noticed that most of time is taken during the execution of the com.crystaldecisions.report.web.viewer.ReportExportControl Object method as shown in following line of code
exportControl.processHttpRequest(request, response, context, null)
We thought the delay in exporting the report to PDF might be the layout of the report and data conversion to PDF for such a bigger volume of data.
Then we investigated the issue and experimented quickly to generate the same report with same result set data from the application using XML, XSL and converted the output XSL-FO to PDF using Apache FOP (Formatting Objects Processor) implementation. The time taken to export the report to PDF is less than 6 seconds. By doing this experiment, it is proved that the issue is not with conversion of data to PDF but it is the performance problem with Business Objects Java JRC API in CR XI R2.
In this regard, I searched for the above issue in the SAP community Network Forums -> Crystal Reports and Xcelsius -> Java Development -> Crystal Reports. But I did not find any answers or solutions for this kind of issue in the forums.
Any suggestion, hint in this matter is very much appreciated.Ted, The setReportAppServer problem is resolved. Now I could able to generate the report with hardcoded values in the SQLs in just 6 seconds where as the same report was generated in CRXI R2 in 1 minute 15 seconds as mentioned in the earlier message.
But, our exisiting application passes the parameter values to the SQLs embedded in the report. For some reason the parameters are not being passed to the report and the report displays only the labels without data.
As per the crj 12 samples codes, the code is written as shown below.
1. Created ReportClient Document
2. SetReportAppServer
3. Open the report
4. Getting DatabaseController and switching the database connection at runtime
5. Then setting the parameters as detailed below
ParameteFields parameterFieldController = reportClientDoc.getDataDefController().getParameterFieldController();
parameterFieldController.setCurrentValue("", "paramname",paramvalue);
parameterFieldController.setCurrentValue("", "paramname",paramavalue);
byteArrayInputStream = (ByteArrayInputStream)reportClientDoc.getPrintOutputController().export(ReportExportFormat.PDF);
6. Streaming the report to the browser
Why the parematers are not being passed to the report? Do I need to follow the order of setting these parameters? Did I miss any line of code for setting Params using crj 12?
Any help in this regard would be greatly appreciated.
Maybe you are looking for
-
Is there a way to change the Windows Update service startup type on Windows Server 2012 R2?
We have a number of newly built 2012 R2 servers that we have HP Operations Manager agent running on that monitors the status of several services and reports if they are "stopped". One of these services is Windows Update. Every day we get at least one
-
Jdeveloper aplic. using Tomcat
I develop an application in Jdeveloper, which runs fine when I open it with the browser. I am able to deploy it to tomcat, but when I open with the brower, I get the following error: Error: 500 Location: /examples/jsp/test2\MyProject1_html/main.jsp I
-
How can I get help to fix I messaging on my I pod touch
Hi this is Kaitlyn now if I sign in to messaging will it work or not let me sign in
-
Hi kauaibirdie, There have been some recent changes for locating the Live Chat option. Check the information in this post to see if it helps.
-
How do I share non-global zone filesystem?
I have a non-global zone that needs to have a UFS local filesystem. That file system also needs to be accessible (via NFS or whatever) to another non-global zone. Can this be done?