I want to weave two class files using AspectJ - ajc, i.e. I want to implement byte code weaving.
Hello.class //it is a java class file
AspectHello.class // it is a aspect class file
How can i implement it on command line?
Thanks in advance
yang
So it should be something like:
ajc -inpath <path to Hello.class> -aspectpath <path to AspectHello.class> -d <path of output directory>
Related
I've used succesfully UA-ModelCompiler from OPCFoundation (https://github.com/OPCFoundation/UA-ModelCompiler) for compiling my xml model, using the following format:
OPC.UA.ModelCompiler.exe -d2 ".\MyOpcUaBasic.xml" -cg ".\MyOpcUaBasic.csv" -o2 ".\MyOutputFolder"
I'd like to compile another OPC UA xml model that uses more than one namespace declared at the beginning of the model.
Example:
<Namespaces>
<Namespace Name="MyOpcUaBasic" Prefix="Opc.Ua.Basic" XmlPrefix="MyOpcUaBasic">http://Myorganization.it/Basic/"</Namespace>
<Namespace Name="MyOpcUaBasic2" Prefix="Opc.Ua.Basic2" XmlPrefix="MyOpcUaBasic2">http://Myorganization.it/Basic2/"</Namespace>
<Namespace Name="OpcUa" Prefix="Opc.Ua" XmlPrefix="OpcUa" XmlNamespace="http://opcfoundation.org/UA/2008/02/Types.xsd">http://opcfoundation.org/UA/</Namespace>
</Namespaces>
So I need more than one xml input to generate my xml nodeset.
I have tried the following:
OPC.UA.ModelCompiler.exe -d2 ".\MyOpcUaBasic.xml" -cg ".\MyOpcUaBasic.csv" -d2 ".\MyOpcUaBasic2.xml" -cg ".\MyOpcUaBasic2.csv" -o2 ".\MyOutputFolder"
But it does not work giving an error.
How should I do?
It is possible the usage is not right, but I have't found how to use more than one input xml to create my nodeset, if this is possible.
Thanks.
Found the solution, I forgot the FilePath field
<Namespace Name="MyOpcUaBasic" Version="1.00" PublicationDate="2020-05-27T00:00:00Z" Prefix="Opc.Ua.SmBasic" XmlPrefix="MyOpcUaBasic" XmlNamespace="http://Myorganization.it/OpcUa/ServicesModel/Basic/Types.xsd" FilePath="MyOpcUaBasic">http://Myorganization.it/Basic/</Namespace>
Is it possible to use variables in Kafka config files like server.properties? I tried ${MY_VAR}, but that didn't work. Getting kind of annoying to update all the paths every time the version changes. I updated some of my batch files to use %~dp0, etc. but that doesn't solve the .properties file issue.
Kafka is using this class for reading reading server configuration (and other configuration files): org.apache.kafka.common.utils.Utils.java
In the code Kafka is using java.util.Properties class for reading properties.
As you can see from documentation it does not support variables in properties.
a little tricky
a sample server.properties
...
zookeeper.connect=$ZOOKEEPER_HOST:$ZOOKEEPER_PORT
...
then crate your own bash start with:
export ZOOKEEPER_HOST=192.168.1.100
export ZOOKEEPER_PORT=2181
### reemplacing with .env values
envsubst "`printf '${%s} ' $(sh -c "env|cut -d'=' -f1")`" < ../config/server.properties > srv.properties
./kafka-server-start.sh srv.properties
Here the project structure cloned from github after compiling on Ubuntu successfully,
javaml
bin
net/sf/javaml/core/Dataset.class
javaml
src
net/sf/javaml/core/Dataset.java
When the following command wa given:
java -ea -classpath /home/shahid/git/javaml/bin:/home/shahid/a_f_w/randoop-3.1.5/randoop-all-3.1.5.jar randoop.main.Main gentests --testclass=net.sf.javaml.core.Dataset --literals-file=CLASSES
It generated the error: "Ignoring interface net.sf.javaml.core.Dataset specified via --classlist or --testclass.
No classes to test
".
while the other command java -ea -classpath /home/shahid/git/java-ml/bin:/home/shahid/a_f_w/randoop-3.1.5/randoop-all-3.1.5.jar randoop.main.Main gentests --testclass=DataSet --literals-file=CLASSESwithout package for other project working perfectly.
Any help will be appretiated.
The error message gives you the answer:
Ignoring interface net.sf.javaml.core.Dataset specified via --classlist or --testclass. No classes to test
You are supposed to provide a class, not an interface, to the --testclass command-line argument.
By passing --testclass=net.sf.javaml.core.Dataset to Randoop, you indicated that you only want Randoop to create objects of type net.sf.javaml.core.Dataset. However, since that is an interface, it cannot be instantiated, and Randoop cannot create any objects, nor any tests.
The following command worked for me:
java -ea -classpath ~/javaml/bin/:~/Randoop/randoop-all-3.1.4.jar randoop.main.Main gentests --testclass=net.sf.javaml.core.Complex --literals-file=CLASSES
#mernst thanks for your kind response.
I am generating the client scala code for an API using the Swagger Edtior. I pasted the json then did a Generate Client/Scala. It gives me a default root package of
io.swagger.client
I can't see any obvious way of specifying something different. Can this be done?
Step (1): Create a file config.json and add following lines and define package names:
{
"modelPackage" : "com.xyz.model",
"apiPackage" : "com.xyz.api"
}
Step (2): Now, pass the above file name along with codegen command with -c option:
$ java -jar swagger-codegen-cli.jar generate -i path/swagger.json -l java -o Code -c path/config.json
Now, it will generate your java packages like com.xyz… instead of default one io.swagger.client…
Run the following command to get information about the supported configuration options
java -jar swagger-codegen-cli.jar config-help -l scala
This will give you information about supported by this generator (Scala in this example):
CONFIG OPTIONS
sortParamsByRequiredFlag
Sort method arguments to place required parameters before optional parameters. (Default: true)
ensureUniqueParams
Whether to ensure parameter names are unique in an operation (rename parameters that are not). (Default: true)
modelPackage
package for generated models
apiPackage
package for generated api classes
Next, define a config.json file with the above parameters:
{
"modelPackage": "your package name",
"apiPackage": "your package name"
}
And supply config.json as input to swagger-codegen using the -c flag.
I am on a project that uses both Mybatis (for persisting java to database) and Mybatis Generator (to automatically generate the mapper xml files and java interfaces from a database schema).
Mybatis generator does a good job at generating the files necessary for basic crud operation.
Context
For some of the tables/classes, we will need more "stuff" (code queries, etc) than the "crud stuff" generated by the MyBatis Generator tool.
Is there any way to have "best of both worlds", i.e use auto generation as as well as "custom code". How do you separate out and structure the "hand edited files" and "automatically generated files".
Proposal
I was thinking about the following, i.e. for table "Foo"
Auto-Generated
FooCrudMapper.xml
interface FooCrud.java
(where "Crud" stands for "Create Read Update Delete")
Hand Edited
FooMapper.xml
interface Foo extends FooCrud
The notion: if the schema changed, you could always safely autogenerate the "Crud" xml and .java files without wiping out any of the custom changes.
Questions
Would mybatis correctly handle this scenario, i.e. would this mapper correctly execute the auto-generated 'crud code'?
FooMapper fooMapper = sqlSession.getMapper(FooMapper.class);
What approach do you recommend?
Edit 1:
* Our db design uses a 'core table' ("element") with other tables 'extending' that table and adding extra attributes (shared key) . I've looked at docs and source concluded that I cannot use Mybatis Generator in conjunction with such 'extension' without any hand editing:
i.e. This does not work.
-ElementMapper extends "ElementCrudMapper"
-FooMapper.xml extends both "ElementCrudMapper" and "FooCrudMapper"
thanks all!
I can seperate out generated files and hand edited files.
I use mybatis-spring and spring to manage dao interfaces. This library allows MyBatis to participate in Spring transactions, takes care of building MyBatis mappers and SqlSessions and inject them into other beans, translates MyBatis exceptions into Spring DataAccessExceptions, and finally, it lets you build your application code free of dependencies on MyBatis, Spring or MyBatis-Spring.
For DAO Interfaces, I write a generic MybatisBaseDao to represent base interface generated by mybatis generator.
public interface MybatisBaseDao<T, PK extends Serializable, E> {
int countByExample(E example);
int deleteByExample(E example);
int deleteByPrimaryKey(PK id);
int insert(T record);
int insertSelective(T record);
List<T> selectByExample(E example);
T selectByPrimaryKey(PK id);
int updateByExampleSelective(#Param("record") T record, #Param("example") E example);
int updateByExample(#Param("record") T record, #Param("example") E example);
int updateByPrimaryKeySelective(T record);
int updateByPrimaryKey(T record);
}
Of course, you can custom your BaseDao according to your demand. For example we have a UserDao, Then you can defind it like this
public interface UserDao extends MybatisBaseDao<User, Integer, UserExample>{
List<User> selectUserByAddress(String address); // hand edited query method
}
For mapper xml files, I create two packages in mapper(.xml) base folder to separate generated files and hand edited files. For UserDao above, I put UserMapper.xml generated by generator in package named 'generated'. I put all hand writing mapper sqls into another UserMapper.xml file in the package named manual. The two mapper files start with the same header <mapper namespace="com.xxx.dao.UserDao" >. Mybatis can scan the xml mapper files to map sql and corresponding interface method automatically.
For generated entities and example objects I overwrite them directly.
I hope the method above can help you!
The Larry.Z solution help me to solve the same problem to separate auto generated from hand edited files. I had a custom folder structure in my project and adapted Larry solution to work in my project and add this answer to help other by use Larry solution adapting it.
The best solution is to add feature to Mybatis generator (MBG) to integrate hand modified xml mapper. MBG had to be added parsing features to add corresponding hand node method to client mapper interface but right now this features do not exist so I use and adapted Larry.Z solution.
In my project I use:
<properties>
...
<java.version>1.7</java.version>
<spring.version>3.2.2.RELEASE</spring.version>
<mybatis.version>3.2.2</mybatis.version>
<mybatis-spring.version>1.2.0</mybatis-spring.version>
<mybatis-generator-core.version>1.3.2</mybatis-generator-core.version>
...
</properties>
My folder structure is:
<base>/dao/: MBG generated dao class
<base>/dao/extended/: Extended generated class (<DaoGeneratedName>Extended)
<base>/sqlmap/: MBG generated client Interface and corresponding xml mapper
<base>/sqlmap/extended/:
hand xml mapper and hand client Interface
(<InterfaceGenerated>Extended extends InterfaceGenerated {...)
<base>/sqlmap/generated/: copy of MBG generated mapper namespace changed
I have configured Mybatis - spring
<bean id="mapperScanner" class="org.mybatis.spring.mapper.MapperScannerConfigurer"
p:basePackage="<base>.sqlmap"
p:sqlSessionTemplate-ref="sqlSessionTemplate"
p:nameGenerator-ref="myBeanNameGenerator"
/>
Implement myBeanNameGenerator only if you need to have custom name like me. In this example you can delete row p:nameGenerator-ref="myBeanNameGenerator"
If all your client Interfaces become extended you can substitute above
p:basePackage="<base>.sqlmap.extended"
(my project configuration is huge so I have extract most important bit )
This is an example of my client interface and mapper hand coded:
import <base>.dao.Countries;
import <base>.sqlmap.CountriesMapper;
import org.apache.ibatis.annotations.Param;
public interface CountriesMapperExtended extends CountriesMapper {
/**
*
* #param code
* #return
*/
Countries selectByCountryCode(#Param("code") String code);
}
Where CountriesMapper is the client interface MBG generated
The hand coded correlated xml mapper is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd">
<mapper namespace="<base>.sqlmap.extended.CountriesMapperExtended">
<select id="selectByCountryCode" parameterType="java.lang.String" resultMap="BaseResultMap">
select
<include refid="Base_Column_List" />
from countries co
where co.countrycode = #{code,jdbcType=VARCHAR}
</select>
</mapper>
To make all work I have to integrate in xml mapper all interface method MBG generated and, to do this, I copied MBG generated xml mapper in <base>/sqlmap/generated/ and change his namespace:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd">
<mapper namespace="<base>.sqlmap.extended.CountriesMapperExtended">
... unchanged ...
</mapper>
The problem raise when db change and I have to use MBG to reflect the new db structure.
So I have create quickly a bash script that watch in <base>/sqlmap/extended/ and check if there is an hand coded xml mapper. If there is hand coded xml mapper, copy corresponding MBG generated changing his namespace.
All this code is not an graceful solution but works.
The bash script overwrite file in <base>/sqlmap/generated/ so, not put in this folder your code.
Make a backup copy of your project and modify the bash script, to custom it and use on your responsibility.
#!/bin/bash
CURDIR="$(pwd)"
SCRIPT_DIR=`dirname $0`
usage()
{
cat << EOF
usage: $0 options
This script is usefull to generate xml map to extend mybatis
generator client interfaces. It suppose this structure:
<base>/sqlmap/ : generated xml mapper and interfaces
<base>/sqlmap/extended/ : extended xml mapper and interfaces
<base>/sqlmap/generated/ : copy of generated xml mapper changing
its namespace
If exist a mapper xml in <base>/sqlmap/extend identify by a name
ending in Extended this script generate a copy of original generated
xml map of extended interface changing then namespace to reflect the
extended Interface in <base>/sqlmap/generated.
This script require a list of base path:
$0 path1 path2 ...
Required parameters are marked by an *
OPTIONS:
-h, --help Show this message
EOF
}
declare -a BASES
let INDEX=0
TEMP=`getopt -o "hb:" --long "help,base:" -n "$0" -- "$#"`
eval set -- "$TEMP"
while true ; do
case "$1" in
-h|--help)
usage
exit 1 ;;
--)
shift ;
break ;;
*)
echo "Too mutch parametes!!! abort." ;
exit 1 ;;
esac
done
#process all paths
let INDEX=0
BASE="$1"
while [ "${BASE:0:1}" == "/" ]
do
shift ;
BASES[$INDEX]="$BASE"
let INDEX+=1
BASE="$1"
done
if [ "$INDEX" -le "0" ]
then
echo "--bases options cannot be emplty"
usage
exit 1
fi
for BASE in ${BASES[#]}
do
if [ ! -d "$BASE" ]
then
echo "Error: every base parameter must be a folder!!"
echo "Base=$BASE is not a folder"
usage
exit 1
fi
SQLMAP="$BASE/sqlmap"
if [ ! -d "$SQLMAP" ]
then
echo "Error: every base parameter must have a sqlmap folder!!"
echo "$SQLMAP is not a folder"
usage
exit 1
fi
EXTENDED="$BASE/sqlmap/extended"
if [ ! -d "$EXTENDED" ]
then
echo "Error: every base parameter must have a sqlmap/extended folder!!"
echo "$EXTENDED is not a folder"
usage
exit 1
fi
GENERATED="$BASE/sqlmap/generated"
if [ ! -d "$GENERATED" ]
then
mkdir -p "$GENERATED"
fi
while IFS= read -r -d '' file
do
name="${file##*/}"
#path="${file%/*}"
ext=".${name##*.}"
nameNoSuffix="${name%$ext}"
nameBase="${nameNoSuffix%Extended}"
sed -r 's/<mapper namespace="(.+)\.([^."]+)"\s*>\s*$/<mapper namespace="\1.extended.\2Extended">/' "$SQLMAP/$nameBase.xml" > "$GENERATED/$nameNoSuffix.xml"
done < <(eval "find $EXTENDED/ -type f -name \*Extended\.xml -print0")
done
exit 0
Use of the script
$ ./post-generator.sh "/home/...<base>" do not put the last / on path
This path is the path to the folder that contains sqlmap, sqlmap/extended, sqlmap/generated
You can use a list of path if you, like me, have more then one
To use it by maven, I use this plugin in project pom.xml:
<plugin>
<artifactId>exec-maven-plugin</artifactId>
<groupId>org.codehaus.mojo</groupId>
<version>1.2.1</version>
<executions>
<execution>
<id>build client extended xml</id>
<goals>
<goal>exec</goal>
</goals>
</execution>
</executions>
<configuration>
<executable>${basedir}/scripts/post-generator.sh</executable>
<workingDirectory>${basedir}/scripts</workingDirectory>
<arguments>
<argument>${basedir}/<basepath1></argument>
<argument>${basedir}/<basepath2></argument>
</arguments>
</configuration>
</plugin>
On project folder you can use $ mvn exec:exec
or $ mvn mybatis-generator:generate exec:exec
If you use Netbeans you can configure a project action to run these goals mybatis-generator:generate exec:exec without left Netbeans. You can start it by hand when you have a change in db structure.
Now you can work on exended mapper without problem and let MBG do his work if db structure change.
In your bean you can inject extended interface that have
automatic generated MBG methods plus your hand coded methods:
<bean id="service" class="<base>.services.ServiceImpl" scope="singleton"
...
p:countriesMapper-ref="countriesMapperExtended"
...
p:sqlSessionTemplate-ref="sqlSessionTemplate"
/>
Where countriesMapperExtended bean is generated by mapperScanner above.
I have give a working answer but it's complex and not easy to understand due to the huge configurations.
Now I have found a better and more concise and easy answer.
I'm inspired by Emacarron's post: Fix #35
I have use mbg and in generatorConfig.xml I put <javaClientGenerator type="XMLMAPPER" ...> to generate java interface and xml map configuration on folder mapper.
so in my example on mapper folder I have:
AnagraficaMapper.java
AnafigraficaMapper.xml
in model folder I have
Anagrafica.java
AnagraficaKey.java
AnagraficaExample.java
The first two are object model and extend they is trivial.
To extends mapper I simply copy and empty
AnagraficaMapper.java --> AnagraficaExMapper.java
AnagraficaMapper.xml --> AnagraficaExMapper.xml
in this two new file I put my new code.
Making an example I decide to add a new sql selectByPrimaryKeyMy
public interface AnagraficaExMapper extends AnagraficaMapper {
Anagrafica selectByPrimaryKeyMy(AnagraficaKey key);
}
This is my interface extending mgb generated AnagraficaMapper interface.
in AnagraficaExMapper.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd">
<mapper namespace="net.algoritmica.ciaomondo.mapper.AnagraficaExMapper" >
<select id="selectByPrimaryKeyMy" parameterType="net.algoritmica.ciaomondo.model.AnagraficaKey" resultMap="net.algoritmica.ciaomondo.mapper.AnagraficaMapper.BaseResultMap">
select
<include refid="net.algoritmica.ciaomondo.mapper.AnagraficaMapper.Base_Column_List" />
from ANAGRAFICA anag
where anag.IDANAGRAFICA = #{idanagrafica,jdbcType=INTEGER}
</select>
</mapper>
How can you see the namespace is ...AnagraficaExMapper pointing to the new extending interface.
By the solution on Fix #35 when MyBatis searched for code in AnagraficaExMapper.java and found selectByPrimaryKeyMy method, this was founded in AnagraficaExMapper.xml too;
but when searched for hierarchic method like selectByPrimaryKey this was not found in AnagraficaExMapper.xml but thank to Fix #35 the code was searched on parent name too, binding all extended interfeces method in the old AnagraficaMapper.xml
To include fragment included in old xml file you have to use a full path to old xml file like in: <include refid="net.algoritmica.ciaomondo.mapper.AnagraficaMapper.Base_Column_List" />
Now you can simply have to configure MyBatis for automatic mapper scan and all interfaces where correctly bounded to xml mapper.
when you use mbg to feel db change the interface was regenerate but new extending interface are not override so your code is save.
regards
I had this task in Spring Boot project and was resolved bellow
In mybatis/*.xml files i changed generated like this <mapper namespace="news.project.demo.mappers.BrandMapper"> to
<mapper namespace="news.project.demo.mappers.extended.BrandMapperExtended">
But all sql logic must be written in xml-files. Interfaces are only declarations without #Select or #ResultMap annotations, so you must configure correctly your mybatis-generator.
in application.properties i have
mybatis.mapper-locations=classpath*:mybatis/*.xml
mybatis.type-aliases-package=news.project.demo.models