You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Dennis Sosnoski (JIRA)" <ji...@apache.org> on 2006/04/10 13:51:02 UTC
[jira] Created: (AXIS2-559) Move JaxMe databinding code into
separate module
Move JaxMe databinding code into separate module
------------------------------------------------
Key: AXIS2-559
URL: http://issues.apache.org/jira/browse/AXIS2-559
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: databinding
Environment: n/a
Reporter: Dennis Sosnoski
As discussed on the axis-dev list, the JaxMe code needs to be moved into a separate module so that code generation only requires the data binding frameworks actually being used to be present in the classpath. See the xmlbeans and jibx modules, along with the corresponding org.apache.axis2.wsdl.codegen.extension code, for examples of how this can be done. The discussion is at http://marc.theaimsgroup.com/?l=axis-dev&m=114336065805196&w=2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-559) Move JaxMe databinding code into
separate module
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577033#action_12577033 ]
Davanum Srinivas commented on AXIS2-559:
----------------------------------------
already removed jaxme.
thanks,
dims
> Move JaxMe databinding code into separate module
> ------------------------------------------------
>
> Key: AXIS2-559
> URL: https://issues.apache.org/jira/browse/AXIS2-559
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: databinding
> Environment: n/a
> Reporter: Dennis Sosnoski
>
> As discussed on the axis-dev list, the JaxMe code needs to be moved into a separate module so that code generation only requires the data binding frameworks actually being used to be present in the classpath. See the xmlbeans and jibx modules, along with the corresponding org.apache.axis2.wsdl.codegen.extension code, for examples of how this can be done. The discussion is at http://marc.theaimsgroup.com/?l=axis-dev&m=114336065805196&w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-559) Move JaxMe databinding code into
separate module
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-559:
-----------------------------------
Assignee: (was: Davanum Srinivas)
> Move JaxMe databinding code into separate module
> ------------------------------------------------
>
> Key: AXIS2-559
> URL: https://issues.apache.org/jira/browse/AXIS2-559
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: databinding
> Environment: n/a
> Reporter: Dennis Sosnoski
>
> As discussed on the axis-dev list, the JaxMe code needs to be moved into a separate module so that code generation only requires the data binding frameworks actually being used to be present in the classpath. See the xmlbeans and jibx modules, along with the corresponding org.apache.axis2.wsdl.codegen.extension code, for examples of how this can be done. The discussion is at http://marc.theaimsgroup.com/?l=axis-dev&m=114336065805196&w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-559) Move JaxMe databinding code into
separate module
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-559:
-----------------------------------
Assignee: Davanum Srinivas
> Move JaxMe databinding code into separate module
> ------------------------------------------------
>
> Key: AXIS2-559
> URL: https://issues.apache.org/jira/browse/AXIS2-559
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: databinding
> Environment: n/a
> Reporter: Dennis Sosnoski
> Assigned To: Davanum Srinivas
>
> As discussed on the axis-dev list, the JaxMe code needs to be moved into a separate module so that code generation only requires the data binding frameworks actually being used to be present in the classpath. See the xmlbeans and jibx modules, along with the corresponding org.apache.axis2.wsdl.codegen.extension code, for examples of how this can be done. The discussion is at http://marc.theaimsgroup.com/?l=axis-dev&m=114336065805196&w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-559) Move JaxMe databinding code into
separate module
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved AXIS2-559.
------------------------------------
Resolution: Fixed
> Move JaxMe databinding code into separate module
> ------------------------------------------------
>
> Key: AXIS2-559
> URL: https://issues.apache.org/jira/browse/AXIS2-559
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: databinding
> Environment: n/a
> Reporter: Dennis Sosnoski
>
> As discussed on the axis-dev list, the JaxMe code needs to be moved into a separate module so that code generation only requires the data binding frameworks actually being used to be present in the classpath. See the xmlbeans and jibx modules, along with the corresponding org.apache.axis2.wsdl.codegen.extension code, for examples of how this can be done. The discussion is at http://marc.theaimsgroup.com/?l=axis-dev&m=114336065805196&w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-559) Move JaxMe databinding code into
separate module
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574624#action_12574624 ]
Davanum Srinivas commented on AXIS2-559:
----------------------------------------
Started a thread on axis-dev to *drop* jaxme databinding.
> Move JaxMe databinding code into separate module
> ------------------------------------------------
>
> Key: AXIS2-559
> URL: https://issues.apache.org/jira/browse/AXIS2-559
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: databinding
> Environment: n/a
> Reporter: Dennis Sosnoski
>
> As discussed on the axis-dev list, the JaxMe code needs to be moved into a separate module so that code generation only requires the data binding frameworks actually being used to be present in the classpath. See the xmlbeans and jibx modules, along with the corresponding org.apache.axis2.wsdl.codegen.extension code, for examples of how this can be done. The discussion is at http://marc.theaimsgroup.com/?l=axis-dev&m=114336065805196&w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org