| Key: |
XMLBEANS-324
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Oskar Carlstedt
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
11/May/07 07:46 PM
|
|
Hello!!
I have som deploying issues that are related to xml beans. Can someone tell me why javax.xml.namespae is included in xbean.jar and xmlpublic.jar. Also, why are these bundeled into xml beans. Isn't it better to leave them as a dependency to xml beans.
Ok, I know that people hate dependencies to other jars - but anyway, today's solution makes me (and a lot of other people too) getting a java.lang.LinkedError when using the QName class.
Is i tpossible to remove these classes ffrom the xml beans distribution.
Best Regards
Oskar Carlstedt
|
|
Description
|
Hello!!
I have som deploying issues that are related to xml beans. Can someone tell me why javax.xml.namespae is included in xbean.jar and xmlpublic.jar. Also, why are these bundeled into xml beans. Isn't it better to leave them as a dependency to xml beans.
Ok, I know that people hate dependencies to other jars - but anyway, today's solution makes me (and a lot of other people too) getting a java.lang.LinkedError when using the QName class.
Is i tpossible to remove these classes ffrom the xml beans distribution.
Best Regards
Oskar Carlstedt
|
Show » |
| No work has yet been logged on this issue.
|
|
Strange contents of JAR-files
