Task #32 (closed)
Opened 13 years ago
Closed 13 years ago
Test Java 1.4 client from Macosx 10.3
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-M2 |
| Component: | Deployment | Version: | 3.0-M1 |
| Keywords: | iteration2 | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Currently there is a restriction on the client-side JVM that we can use placed by what is available on Macosx 10.3 ( < Java5 ). We need to make sure that these clients can even run against a Java5 server before letting this block the migration to Java5 on the client-side.
Change History (3)
comment:1 Changed 13 years ago by jmoore
- Component changed from api to deployment
comment:2 Changed 13 years ago by Josh Moore <josh.moore@…>
- Milestone cycle2 deleted
comment:3 Changed 13 years ago by jmoore
- Keywords iteration2 added
- Milestone changed from Unscheduled to 3.0-M2
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
We will need to architect a different solution for using the upcoming remoting infrastructure, but it won't be a straight Java 1.4 client talking to Java 5 server, but rather an intermediary broker with two separate object models (hopefully all code-generated).
Moving this out of cycle 2 until we know when remoting is going to get done.