nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

upgrade from 1.3 to 2.3.1 API for Flex results in repeat component definition errors

JanicePeal

We are in the process of upgrading our flex api from 1.3 (agslib-1.3-2009-10-31.swc) to 2.3.1 for a complex mapping application. What used to work with no build errors is now throwing the following error:

"component FeatureSet is defined more than once in this namespace. Remove the mapping to com.esri.ags:FeatureSet or com.esri.ags.tasks:FeatureSet"

with an unknown location indicated. However it does point to the parent application. I have no idea where to start looking to fix this. I tried to repoint old imports to the new library location in my projects and this error still exists. Has anyone encountered an error such as this during an upgrade, and if so, what did you do? Any help would be greatly appreciated. Thank you!

Encontre mais publicações marcadas com

Accepted answers

All comments

RobertScheitlin__GISP

Janice,

It sounds like you have the old and the new API referenced in your project. Check your libs folder and ensure you only have the latest API swc that you want to use there.

JanicePeal

Thank you for your reply. I checked this in the Referenced Libraries in the project and there are no references to the old library. I am at a loss as to what to do next. Is there somewhere else (besides the Flex Build Path folder under the project's Properties) I should be looking?

RobertScheitlin__GISP

Janice,

What about in the libs folder under the src folder in the package explorer tree.

JanicePeal

I don't have a libs folder there. Should I? The only libs folder I have in that project is under the root, with a sub-folder called air that has an assortment of swfs and js files (we're not running in air).
Oh wait...I found a lib folder under bin with a bunch of jar and txt files...would a reference to the library be in there?

I know the framework of this application is OLD, so even the build folders look different than a freshly started project in 4.5.Our programmer left and it's up to me to figure this out (I'm a newbie to this). Thanks for your guidance.

RobertScheitlin__GISP

Janice,

I was wrong it is under the root of the project not the src folder. So you need to check there is there is a older agslib-***.swc and if there is delete it. Then From the Project menu run a "clean" command.

JanicePeal

Janice,

I was wrong it is under the root of the project not the src folder. So you need to check there is there is a older agslib-***.swc and if there is delete it. Then From the Project menu run a "clean" command.

I checked ALL over the project and the library that is also linked to said project and found no reference to the old library anywhere. Any more ideas? I've spent the past month learning how to upgrade a web server....this is just one more hideous nuisance in my upgrade process. Thanks again.

RobertScheitlin__GISP

Janice,

Try to run the "clean" command form the "Project" Menu and then check the "problems" window (if the problems window is not displayed than enable it from the "Window" menu than "Show View" and "Problems").

JanicePeal

Sorry, I neglected to mention that I did run the "clean" on the project and the error still exists. Maybe I just have to start a new project from scratch and copy/paste the code back in. Perhaps that will fix it. I'll give that a shot and let you know how I make out. Thanks again for your guidance.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.