The Java template is evolved by supporting Apache Kafka other than IBM MQ (with JMS).
For this reason, I think that it does make more sense to have as default Java package for the generated code something more general like com.asyncapi (I see it being used in the Java Sprint template as well) instead of a more specific com.ibm.mq.samples.jms (IBM MQ with JMS).
When using the template for Apache Kafka clients, having the generated code under com.ibm.mq.samples.jms by default sounds weird.
Of course, this can be changed providing the package as parameter to the generator but anyway having the current default package name doesn't seems to be right.
The Java template is evolved by supporting Apache Kafka other than IBM MQ (with JMS). For this reason, I think that it does make more sense to have as default Java package for the generated code something more general like
com.asyncapi
(I see it being used in the Java Sprint template as well) instead of a more specificcom.ibm.mq.samples.jms
(IBM MQ with JMS). When using the template for Apache Kafka clients, having the generated code undercom.ibm.mq.samples.jms
by default sounds weird. Of course, this can be changed providing the package as parameter to the generator but anyway having the current default package name doesn't seems to be right.