Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 3.0.5, 3.0.6, 3.1, 3.1.1, 4.0.0
-
Fix Version/s: 4.2.0
-
Component/s: Configuration
-
Security Level: Public
-
- Description:
-
Hide
NOTE : I am currently working on Petals ESB extensibility and lighweight (in memory) mode and I think I will share in the JIRA as improvment entries some problems I encounter.
In petals-kernel : org.ow2.petals.kernel.configuration.ConfigurationServiceImpl#start, the server.properties file is retrieved from the classloader, a File object is then created (File serverPropsFile = new File(serverPropsURL.toURI().normalize())
and the file is not used but a stream is created from it.
This type of handling does not allow using a server.properties file elsewhere than in the conf folder, using a server.properties as JAR resource raise an exception :Caused by: org.objectweb.fractal.api.control.IllegalLifeCycleException: URI is not hierarchical
Solution is to not create the file since it is not used, getting the input stream is enough.
ShowNOTE : I am currently working on Petals ESB extensibility and lighweight (in memory) mode and I think I will share in the JIRA as improvment entries some problems I encounter. In petals-kernel : org.ow2.petals.kernel.configuration.ConfigurationServiceImpl#start, the server.properties file is retrieved from the classloader, a File object is then created (File serverPropsFile = new File(serverPropsURL.toURI().normalize()) and the file is not used but a stream is created from it.
This type of handling does not allow using a server.properties file elsewhere than in the conf folder, using a server.properties as JAR resource raise an exception :
Caused by: org.objectweb.fractal.api.control.IllegalLifeCycleException: URI is not hierarchical
Solution is to not create the file since it is not used, getting the input stream is enough.
-
- Environment:
- *
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Admin [ rnaudin ] | |
| Priority | Major [ 3 ] | |
| Component/s | Configuration [ 10257 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Assignee | Christophe DENEUX [ cdeneux ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 4.2.0 [ 10356 ] | |
| Resolution | Won't Fix [ 2 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Your problem has been fixed moving the read of the server.properties at the petals-launcher level. So you can write your own launcher according to your needs.