bsorrentino / bean-manager Goto Github PK

example:

class A {}

@Entity
class B extends A  {}

@Entity
class C extends B {}

in this case also the attributes of class A are considered persistent

to avoid to have wrong java syntax during bean generation we have to trim
column name

Send request to SONATYPE to have permission to publish beanManager to PUBLIC 
MAVEN REPO

[https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usag
e+Guide]

What steps will reproduce the problem?
1.Declare the depency and compile
2.
3.

What is the expected output? What do you see instead?

Maven can't find the following artifact:

org.eclipse.osgi:org.eclipse.osgi:jar:3.2.0-v20060601

What version of the product are you using? On what operating system?

I have used the following artifacts:

<groupId>org.bsc.framework</groupId>
<artifactId>beanmanager-jpa</artifactId>
<version>1.4</version>

<groupId>org.bsc.framework</groupId>
<artifactId>beanmanager-core</artifactId>
<version>1.4</version>




Please provide any additional information below.

The stacktrace of the error:

Missing:
----------
1) org.eclipse.osgi:org.eclipse.osgi:jar:3.2.0-v20060601

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.eclipse.osgi -DartifactId=org.eclipse.osgi -Dversion=3.2.0-v20060601 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=org.eclipse.osgi -DartifactId=org.eclipse.osgi -Dversion=3.2.0-v20060601 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) it.soulsoftware:amplifon-gwt:war:1.1-SNAPSHOT
        2) it.soulsoftware:amplifon-services:jar:1.1-SNAPSHOT
        3) org.bsc.framework:beanmanager-core:jar:1.4
        4) org.eclipse.osgi:org.eclipse.osgi:jar:3.2.0-v20060601

----------
1 required artifact is missing.

for artifact:
  it.soulsoftware:amplifon-gwt:war:1.1-SNAPSHOT

from the specified remote repositories:
  gwtupload (http://gwtupload.googlecode.com/svn/mavenrepo/),
  central (http://repo1.maven.org/maven2),
  java.net (http://download.java.net/maven/2/),
  google-bean-manager (http://bean-manager.googlecode.com/svn/trunk/mavenrepo),
  apache-repo-snapshots (https://repository.apache.org/content/repositories/snapshots/),
  apache-repo (https://repository.apache.org) 


As workaround, i have excluded the artifact from the dependency :

<exclusions>
     <exclusion>
    <artifactId>org.eclipse.osgi</artifactId>
    <groupId>org.eclipse.osgi</groupId>
     </exclusion>
</exclusions> 

add support of DynaPropertyDescriptorJoin 

This issue is designed for JPA user. Idea is to allow put a default.schema 
property in BeanManager.properties

if schema is not defined the default schema (if set) will be used

In Wizard the generate bean name must have the firt letter in upper case

release will be deployed in http://download.java.net/maven/2/ repository

add support for schema attribute in @Table annotation

@Table( schema="", name="" )

Idea is to support a sub-set of java persistent annotation

to facilitate code portability in different J2EE environment

Create how to to manage dynamic bean (like map) from BeanManager

Integrate cglib http://cglib.sourceforge.net to improve reflection usage

moreover 

evaluate the possibility to enhance class (JPA concern)

change BeanManager interface to support create 

from 

public int create( Connection conn, Object bean ) throws SQLException;

to

public int create( Connection conn, Object... bean ) throws SQLException;

This issue is designed for JPA user. Idea is to allow put ${...} variables in 
schema or table name definition

The variables will be matched with both Configurator properties or System 
properties
es:

@Table( name="MYTABLE", schema="${global.schema}" )
class MyEntity {}

I have do a search on a join with extension fields.
I Know that I can do it differently, but I'd like know if possible to do 
it automatically.
Thank's

In order to avoid to provide custom annotations (we want keep only standard JPA 
annotation), idea is to provide a customizer interface on the BeanManager 
creation

JPABeanManagerFactory.createBeanManager(MyBean.class, new Customizer() {

      public PropertyDescriptorField process( PropertyDescriptorField pd ) {
            // process
            return pd;
      }
});

Add Method in BeanManagerUtils to map sql Type (java.sq.Type) to java class

I had build all my code but I recive the follow error:
[ERROR]symbol  : method aggregateProperties
(java.lang.Class<it.softphone.sipvr.extgwt.client.services.RecFileBean>,jav
a.beans.PropertyDescriptor[],java.beans.BeanInfo[])
[ERROR]location: class org.bsc.bean.BeanManagerUtils

My be, I can not download the latest version of BeanManager.

Thanks in advance

Actually if use JPA extension and set a property as java.uil.Date the 
BeanManager treat it as BLOB

workaround is to use java.sql.Date (not acceptable for GWT-RPC protocol)

Create a wizard that , Using ddlutils, allow to create DB Schema and
(optionally) the related beanInfo(s)

What about using the DDLWizard using a sql file instead of the XML file?

I got exception to pass as attribute's type an InputStreamReader from
CLOBAdapter

idea is to provide the following methods:

BeanManagerUtils.registerAdapter( Class<?> type, DataAdapter adapter )
BeanManagerUtils.unregisterAdapter( Class<?> type )

Es.:

        CharBooleanAdapter adapter = new CharBooleanAdapter();

        BeanManagerUtils.registerAdapter( Boolean.TYPE, adapter);
        BeanManagerUtils.registerAdapter( Boolean.class, adapter);

Add an auto-generated field feature

Will be posssible to Generator function to a field  

add support for @MappedSuperclass annotation 

add support for InheritanceType=SINGLE_TABLE

add support for non-entity inheritance

remove constants from JoinnRelations class

create an enum JoinType

change parameter in BeanDescriptorEntity.createJoinRelation

Add a utility class to facilitate use of transaction

es.:

TransactionUtils.exec( connection, new TransactionExecutor() {

     public void exec( Connection c ) throws SQLException {

                // perfrom something without taking care of open,close, commit, rollback
     }

});

change BeanManager interface to support create 

from 

public int create( Connection conn, Object bean ) throws SQLException;

to

public int create( Connection conn, Object... bean ) throws SQLException;

When the bean property's type is char[] and the db type is CLOB the
CLOBAdapter.getValue() method fail 

Idea is to add adapter both at class level and property/attribute level

Example:

@Entity
@DataAdapter( type=Boolean.class, 
class="org.bsc.framework.adapters.CharBoolean")
class MyBean {


@DataAdapter(class="TrimAdapter")
private String value;

@DataAdapter(class="NumberStringAdapter")
public int getNumber() {}

}

provide new method BeanManagerFactory.getSPIFactory() using ServiceLoader

the java 1.5 compatibility will be broken

IDEA is to provide a method to add Join directly from BeanInfo of interest

e.g.


BeanManagerUtils.addPropertiesJoin( properties, new JoinedBeanInfo() )  

Idea is to Develop a Java Processor that generate SQL for database creation and 
join it with the http://code.google.com/p/maven-annotation-plugin/ in order to 
use use it from maven

method 
public Object getValue(ResultSet resultSet, PropertyDescriptorField
PropertyDescriptorField) throws SQLException ;

of CharBooleanAdapter return always true;