-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Takahide,

Does it make sense to trigger the expanion when getNamespace() is called?

thanks,
dims

Takahide Nogayama wrote:
| Hi folks,
|
| I am facing prefix mismatch problem of OMSourcedElement. If we get a
| prefix from non-expanded OMSE by using OMSE.getNamespace().getPrefix(),
| the returned prefix is "". But if we get the prefix from expanded OMSE,
| then the returned prefix is "ns1". The first default OMNamespace is set by
| OMSE creater (can be outside of axiom and axis2) through constructor
| argument, The second OMNamespace is created from OMDatasource when it is
| expanded. Since these two OMNamespace are created by different ways, the
| prefixes can be mismatch.
|
| OMSourcedElement should return the same data regardless of whether it is
| expanded or not. I think the OMNamespace should not be provided by
| Constructor, but should be provided by OMDataSource to avoid such prefix
| mismatch, otherwise we have to expand OMSourcedElement when getNamespace()
| is invoked. I am not sure there are other ways to avoid this problem...
|
| Let me know your comments.
|
| Regards,
| ---------------------------
| Takahide Nogayama, IBM Tokyo Research Laboratory
| E-mail: [EMAIL PROTECTED]
| ---------------------------
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIa3nwgNg6eWEDv1kRAkPDAJwLFZdNGDxZCM4Dw3fjlX8tBi1QSgCePtc0
JWecKvm+rRNlmAjm+flSJNA=
=ztK8
-----END PGP SIGNATURE-----

Reply via email to