
|
If you were logged in you would be able to see more operations.
|
|
|
|
If a service's interfaces are delcared to have > 1 resource, the resulting parsed ClassBundles are wrong. For example:
(XML)
<ServiceBean Name='RaytraceService' Fork='yes'>
<Interfaces>
<Interface>net.gomez.raytraceservice.RaytraceService</Interface>
<Resources>
<JAR>lib/arl/arl-support.jar</JAR>
<JAR>lib/arl/arl-brlcadservice-dl.jar</JAR>
</Resources>
<Resources ref='client.jars'/>
</Interfaces>
...
</ServiceBean>
Will result in 2 ClassBundles being created instead of one.
The groovy parser does not handle this correctly. This is most likely due to the support that the interfaces element may have > 1 interface classes, each with it's own ClassBundle.
|
|
Description
|
If a service's interfaces are delcared to have > 1 resource, the resulting parsed ClassBundles are wrong. For example:
(XML)
<ServiceBean Name='RaytraceService' Fork='yes'>
<Interfaces>
<Interface>net.gomez.raytraceservice.RaytraceService</Interface>
<Resources>
<JAR>lib/arl/arl-support.jar</JAR>
<JAR>lib/arl/arl-brlcadservice-dl.jar</JAR>
</Resources>
<Resources ref='client.jars'/>
</Interfaces>
...
</ServiceBean>
Will result in 2 ClassBundles being created instead of one.
The groovy parser does not handle this correctly. This is most likely due to the support that the interfaces element may have > 1 interface classes, each with it's own ClassBundle. |
Show » |
made changes - 26/Mar/09 06:39 PM
| Field |
Original Value |
New Value |
|
Status
|
Open
[ 1
]
|
In Progress
[ 3
]
|
made changes - 26/Mar/09 07:17 PM
|
Status
|
In Progress
[ 3
]
|
Open
[ 1
]
|
made changes - 15/Apr/09 01:57 PM
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|