| Anonymous | Login | Signup for a new account | 10-31-2025 06:43 PDT | 
| Main | My View | View Issues | Change Log | Docs | 
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0004175 | [Resin] | minor | always | 08-11-10 13:06 | 08-16-10 14:27 | ||||
| Reporter | ferg | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | |||||||
| Summary | 0004175: duplicate @HessianService/@Singleton | ||||||||
| Description | (rep by Jeff Schnitzer) There seems to still be a problem with singletons exposed as hessian services. I can create a test project if necessary, but I'm seeing this behavior in two separate applications: 1) Create a @Singleton bean 2) Give the bean a @Startup @PostConstruct method that initializes some data 3) Give the bean a @HessianService annotation 4) Call the bean via hessian 5) Observe that the data isn't initialized This was a problem long ago in 4.0.0 (with the equivalent annotations at the time) but I thought it was fixed sometime later. I could be wrong about that though. The old workaround was to have the hessian endpoint on a different bean which itself injects the singleton. | ||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|  | |||||||||
| Mantis 1.0.0rc3[^]
	Copyright © 2000 - 2005 Mantis Group
	30 total queries executed. 26 unique queries executed. |