|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4175 | minor | always | 08-11-10 13:06 | 08-16-10 14:27 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.10 | ||
|
|
|||||
| 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. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||