Autowire third party jar using annotation in spring
up vote
0
down vote
favorite
I'm building a library which will be used by multiple clients. It's spring based library. I'm testing this library by adding as a dependency in another web application.
package com.mypackage;
@Configuration
@PropertySource("classpath:abc.properties")
@ComponentScan(basePackages = "com.abc.xyz")
public class AppConfig {
@Value("${myprod.password}")
private String password;
@Value("${{myprod.timeout}")
private String timeout;
@Bean
public BeanA beanA() {
BeanA beanA = new BeanA();
....
return beanA;
}
@Bean
public BeanB beanB() {
BeanB beanB = new BeanB();
beanB.setBeanB(beanA());
return beanB;
}
}
I have an AppManager in which I'm injecting BeanB
@Component
public class AppManager {
@Autowired
BeanB beanB;
public void myMethod(){
beanB.<some_method>();
....
}
}
The above code is bundled as a jar and included in a web application as a dependency. Below is the code on Web application side which is acting as Client for this jar.
@ComponentScan(basePackages = "com.mypackage")
public class Client {
private static ApplicationContext applicationContext;
public static void main(String args) {
applicationContext = new AnnotationConfigApplicationContext(Client.class);
AppManager appManager = applicationContext.getBean(AppManager.class);
appManager.myMethod(...);
}
}
Couple of questions -
- If I don't specify the
@ComponentScan(basePackages = "com.mypackage")I getNo qualifying bean of type AppManagererror. How can I avoid@ComponentScanon the package? This is a shared jar with multiple clients, I don't want each client to be aware of the package which need to be scanned. - Can I just autowire the
AppManagerinClientrather than gettingApplicationContextand then bean?
I was hoping the client class to be like -
public class Client {
@Autowired
private AppManager appManager;
public void aMethdod() {
appManager.myMethod(...);
}
}
java spring
asked Nov 19 at 19:59
Pankaj
1,42083065
|
show 1 more comment
up vote
0
down vote
favorite
I'm building a library which will be used by multiple clients. It's spring based library. I'm testing this library by adding as a dependency in another web application.
package com.mypackage;
@Configuration
@PropertySource("classpath:abc.properties")
@ComponentScan(basePackages = "com.abc.xyz")
public class AppConfig {
@Value("${myprod.password}")
private String password;
@Value("${{myprod.timeout}")
private String timeout;
@Bean
public BeanA beanA() {
BeanA beanA = new BeanA();
....
return beanA;
}
@Bean
public BeanB beanB() {
BeanB beanB = new BeanB();
beanB.setBeanB(beanA());
return beanB;
}
}
I have an AppManager in which I'm injecting BeanB
@Component
public class AppManager {
@Autowired
BeanB beanB;
public void myMethod(){
beanB.<some_method>();
....
}
}
The above code is bundled as a jar and included in a web application as a dependency. Below is the code on Web application side which is acting as Client for this jar.
@ComponentScan(basePackages = "com.mypackage")
public class Client {
private static ApplicationContext applicationContext;
public static void main(String args) {
applicationContext = new AnnotationConfigApplicationContext(Client.class);
AppManager appManager = applicationContext.getBean(AppManager.class);
appManager.myMethod(...);
}
}
Couple of questions -
- If I don't specify the
@ComponentScan(basePackages = "com.mypackage")I getNo qualifying bean of type AppManagererror. How can I avoid@ComponentScanon the package? This is a shared jar with multiple clients, I don't want each client to be aware of the package which need to be scanned. - Can I just autowire the
AppManagerinClientrather than gettingApplicationContextand then bean?
I was hoping the client class to be like -
public class Client {
@Autowired
private AppManager appManager;
public void aMethdod() {
appManager.myMethod(...);
}
}
java spring
asked Nov 19 at 19:59
Pankaj
1,42083065
You cannot auto wire static fields.
– M. Deinum
Nov 19 at 20:03
@M.Deinum - Corrected my question - I was testing it with a Main class but finally implementation would be a using non static member
– Pankaj
Nov 19 at 20:07
I still seestatic. Nonetheless you still need something that creates the bean (theApplicationContext) and they need to, at least know what the main configuration is they need to load (you can do that without an@ComponentScan). But either way they need to detect your config (which should create yourAppManager) or scan everything.
– M. Deinum
Nov 19 at 20:12
if your beans are scanned by spring, they will be available in your app context, so you can autowire them where ever you want inside you app.
– slimane
Nov 19 at 20:12
1
By using either@Importto import the additional configuration, or by creating theApplicationContextusing that class as, instead of what you have nowCliënt.class.
– M. Deinum
Nov 19 at 20:48
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm building a library which will be used by multiple clients. It's spring based library. I'm testing this library by adding as a dependency in another web application.
package com.mypackage;
@Configuration
@PropertySource("classpath:abc.properties")
@ComponentScan(basePackages = "com.abc.xyz")
public class AppConfig {
@Value("${myprod.password}")
private String password;
@Value("${{myprod.timeout}")
private String timeout;
@Bean
public BeanA beanA() {
BeanA beanA = new BeanA();
....
return beanA;
}
@Bean
public BeanB beanB() {
BeanB beanB = new BeanB();
beanB.setBeanB(beanA());
return beanB;
}
}
I have an AppManager in which I'm injecting BeanB
@Component
public class AppManager {
@Autowired
BeanB beanB;
public void myMethod(){
beanB.<some_method>();
....
}
}
The above code is bundled as a jar and included in a web application as a dependency. Below is the code on Web application side which is acting as Client for this jar.
@ComponentScan(basePackages = "com.mypackage")
public class Client {
private static ApplicationContext applicationContext;
public static void main(String args) {
applicationContext = new AnnotationConfigApplicationContext(Client.class);
AppManager appManager = applicationContext.getBean(AppManager.class);
appManager.myMethod(...);
}
}
Couple of questions -
- If I don't specify the
@ComponentScan(basePackages = "com.mypackage")I getNo qualifying bean of type AppManagererror. How can I avoid@ComponentScanon the package? This is a shared jar with multiple clients, I don't want each client to be aware of the package which need to be scanned. - Can I just autowire the
AppManagerinClientrather than gettingApplicationContextand then bean?
I was hoping the client class to be like -
public class Client {
@Autowired
private AppManager appManager;
public void aMethdod() {
appManager.myMethod(...);
}
}
java spring
asked Nov 19 at 19:59
Pankaj
1,42083065
I'm building a library which will be used by multiple clients. It's spring based library. I'm testing this library by adding as a dependency in another web application.
package com.mypackage;
@Configuration
@PropertySource("classpath:abc.properties")
@ComponentScan(basePackages = "com.abc.xyz")
public class AppConfig {
@Value("${myprod.password}")
private String password;
@Value("${{myprod.timeout}")
private String timeout;
@Bean
public BeanA beanA() {
BeanA beanA = new BeanA();
....
return beanA;
}
@Bean
public BeanB beanB() {
BeanB beanB = new BeanB();
beanB.setBeanB(beanA());
return beanB;
}
}
I have an AppManager in which I'm injecting BeanB
@Component
public class AppManager {
@Autowired
BeanB beanB;
public void myMethod(){
beanB.<some_method>();
....
}
}
The above code is bundled as a jar and included in a web application as a dependency. Below is the code on Web application side which is acting as Client for this jar.
@ComponentScan(basePackages = "com.mypackage")
public class Client {
private static ApplicationContext applicationContext;
public static void main(String args) {
applicationContext = new AnnotationConfigApplicationContext(Client.class);
AppManager appManager = applicationContext.getBean(AppManager.class);
appManager.myMethod(...);
}
}
Couple of questions -
- If I don't specify the
@ComponentScan(basePackages = "com.mypackage")I getNo qualifying bean of type AppManagererror. How can I avoid@ComponentScanon the package? This is a shared jar with multiple clients, I don't want each client to be aware of the package which need to be scanned. - Can I just autowire the
AppManagerinClientrather than gettingApplicationContextand then bean?
I was hoping the client class to be like -
public class Client {
@Autowired
private AppManager appManager;
public void aMethdod() {
appManager.myMethod(...);
}
}
java spring
java spring
asked Nov 19 at 19:59
Pankaj
1,42083065
asked Nov 19 at 19:59
Pankaj
1,42083065
edited Nov 19 at 20:13
asked Nov 19 at 19:59
Pankaj
1,42083065
asked Nov 19 at 19:59
Pankaj
1,42083065
asked Nov 19 at 19:59
Pankaj
1,42083065
1,42083065
You cannot auto wire static fields.
– M. Deinum
Nov 19 at 20:03
@M.Deinum - Corrected my question - I was testing it with a Main class but finally implementation would be a using non static member
– Pankaj
Nov 19 at 20:07
I still seestatic. Nonetheless you still need something that creates the bean (theApplicationContext) and they need to, at least know what the main configuration is they need to load (you can do that without an@ComponentScan). But either way they need to detect your config (which should create yourAppManager) or scan everything.
– M. Deinum
Nov 19 at 20:12
if your beans are scanned by spring, they will be available in your app context, so you can autowire them where ever you want inside you app.
– slimane
Nov 19 at 20:12
1
By using either@Importto import the additional configuration, or by creating theApplicationContextusing that class as, instead of what you have nowCliënt.class.
– M. Deinum
Nov 19 at 20:48
|
show 1 more comment
You cannot auto wire static fields.
– M. Deinum
Nov 19 at 20:03
@M.Deinum - Corrected my question - I was testing it with a Main class but finally implementation would be a using non static member
– Pankaj
Nov 19 at 20:07
I still seestatic. Nonetheless you still need something that creates the bean (theApplicationContext) and they need to, at least know what the main configuration is they need to load (you can do that without an@ComponentScan). But either way they need to detect your config (which should create yourAppManager) or scan everything.
– M. Deinum
Nov 19 at 20:12
if your beans are scanned by spring, they will be available in your app context, so you can autowire them where ever you want inside you app.
– slimane
Nov 19 at 20:12
1
By using either@Importto import the additional configuration, or by creating theApplicationContextusing that class as, instead of what you have nowCliënt.class.
– M. Deinum
Nov 19 at 20:48
You cannot auto wire static fields.
– M. Deinum
Nov 19 at 20:03
You cannot auto wire static fields.
– M. Deinum
Nov 19 at 20:03
@M.Deinum - Corrected my question - I was testing it with a Main class but finally implementation would be a using non static member
– Pankaj
Nov 19 at 20:07
@M.Deinum - Corrected my question - I was testing it with a Main class but finally implementation would be a using non static member
– Pankaj
Nov 19 at 20:07
I still see
static. Nonetheless you still need something that creates the bean (the ApplicationContext) and they need to, at least know what the main configuration is they need to load (you can do that without an @ComponentScan). But either way they need to detect your config (which should create your AppManager) or scan everything.– M. Deinum
Nov 19 at 20:12
I still see
static. Nonetheless you still need something that creates the bean (the ApplicationContext) and they need to, at least know what the main configuration is they need to load (you can do that without an @ComponentScan). But either way they need to detect your config (which should create your AppManager) or scan everything.– M. Deinum
Nov 19 at 20:12
if your beans are scanned by spring, they will be available in your app context, so you can autowire them where ever you want inside you app.
– slimane
Nov 19 at 20:12
if your beans are scanned by spring, they will be available in your app context, so you can autowire them where ever you want inside you app.
– slimane
Nov 19 at 20:12
1
1
By using either
@Import to import the additional configuration, or by creating the ApplicationContext using that class as, instead of what you have now Cliënt.class.– M. Deinum
Nov 19 at 20:48
By using either
@Import to import the additional configuration, or by creating the ApplicationContext using that class as, instead of what you have now Cliënt.class.– M. Deinum
Nov 19 at 20:48
|
show 1 more comment
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381793%2fautowire-third-party-jar-using-annotation-in-spring%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381793%2fautowire-third-party-jar-using-annotation-in-spring%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You cannot auto wire static fields.
– M. Deinum
Nov 19 at 20:03
@M.Deinum - Corrected my question - I was testing it with a Main class but finally implementation would be a using non static member
– Pankaj
Nov 19 at 20:07
I still see
static. Nonetheless you still need something that creates the bean (theApplicationContext) and they need to, at least know what the main configuration is they need to load (you can do that without an@ComponentScan). But either way they need to detect your config (which should create yourAppManager) or scan everything.– M. Deinum
Nov 19 at 20:12
if your beans are scanned by spring, they will be available in your app context, so you can autowire them where ever you want inside you app.
– slimane
Nov 19 at 20:12
1
By using either
@Importto import the additional configuration, or by creating theApplicationContextusing that class as, instead of what you have nowCliënt.class.– M. Deinum
Nov 19 at 20:48