Excessive Name Conflicts

Hi,
I have iTunes running on two seperate Windows 7 laptops and am unable to share between these. I am also seeing multiple error messages per second in the event viewer from Bonjour services.
mDNSCoreReceiveResponse: Received from 192.168.1.130:50894 22 26AD664146XXXXXX.touch-able.tcp.local. SRV 0 0 3689 Colorado.local.
mDNSCoreReceiveResponse: ProbeCount 2; will rename 18 26AD664146XXXXXX.touch-able.tcp.local. SRV 0 0 3689 Utah.local.
Excessive name conflicts (32) for 26AD664146XXXXXX.touch-able.tcp.local. (SRV); rate limiting in effect
I have the latest version of iTunes and Bonjour installed.
Has anyone seen this or know how to resolve it ? I am also unable to get
iPhone Remote working with both iTunes libraries at the same time.
I have checked the Library Persistent ID on both itunes installs (.itl and .xml)
and these are different.
Thanks
John

I'm seeing multiple errors from Bonjour, also, on both my Win 7 and XP laptops.
They are different from the ones you posted:
492: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)
The number in front cycles through different values: 520,576, 240, 536, 236, 560, 492, 516, 568. Always a burst of ten of them with different numbers.

Similar Messages

Excessive name conflicts (451) for Bonjour in event logs

I have a few hundred PC laptops using iTunes, Bonjour, and AirPlay. Teachers are using iPads and AirPlay to project to pc Laptop and projector. The AirPlay works most of the time and stays active on the pc, but cannot be found by iPads after it is idle for a while. I am getting many errors indicating Excessive Name Conflicts (451) in the event logs. The exact message on one laptop is:
Excessive name conflicts (451) for HS2105._airplay._tcp.local. (SRV); rate limiting in effect
HS2105 is the workstation name. The laptop and iPad are on the same VLAN and multicasting is enabled on WAPs. I think Bonjour is the problem. Any ideas?

I'm seeing multiple errors from Bonjour, also, on both my Win 7 and XP laptops.
They are different from the ones you posted:
492: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)
The number in front cycles through different values: 520,576, 240, 536, 236, 560, 492, 516, 568. Always a burst of ten of them with different numbers.

PI 7.0 - SMICM - Host Name - Conflict with other places

Hi Friends,
We have host name conflict in SMICM and in other places.
For example, in SMICM it shows the host name 'A' for HTTP protocol and it is green, where as in other places like in RZ10 (Profiles in ABAP), Exchange Profiles (Connection Parameters, Host name), in SLD and in Visual Admin the host name is mentioned as 'B'.
At present, the messages are failing in SXMB_MONI with the error "CLIENT_RECEIVE_FAILED 402 ICM_HTTP_TIMEOUT ".
When we checked the paramter "icm/host_name_full" in RZ11,it shows the empty value.
This problem comes in our quality PI system, ABAP stack.
Could you kindly clarify in SMICM for the HTTP service from where the host name is taken and displays here?
Kind regards,
Jegathees P.

Connect to the operating system. Check this file (replace xxx with your SID and, if applicable, 00 with the correct instance):
C:\usr\sap\xxx\SYS\profile\xxx_DVEBMGS00_ILBNKxxx
Find this line:
icm/host_name_full = hostname.company.corp
Is this maybe empty / incorrect / incomplete?
After changing this the server needs to be restarted.
Sometimes we had strange behaviors after host name changes, which went away after going to sicf -> execute -> right-click on default host -> deactivate -> right-click again -> activate -> in the pop-up click the second activate button, which is for activating the system and all dependent entries.

"recording name conflict" error

Hi,
I have a dependency problem building a new copy of Heimdal Kerberos (SS12.1 on SPARC) that I don't know how to work around. When make begins linking a number of the shared libraries together, it bombs out with:
ld: fatal: recording name conflict: file `../krb5/.libs/libkrb5.so' and file `/opt/heimdal/lib/sparcv9/libkrb5.so' provide identical dependency names: libkrb5.so.25 (possible multiple inclusion of the same file)
Libtool is finding /opt/heimdal/lib/sparcv9/libkrb5.so, listed in an .la file for openldap. But, since I built a new version of libkrb5.so, located at ../krb5/.libs/libkrb5.so, it fails. I tried to rename the old directory, but then it fails when it can't find it:
ggrep: /opt/heimdal/lib/sparcv9/libgssapi.la: No such file or directory
/opt/gnu/bin/sed: can't read /opt/heimdal/lib/sparcv9/libgssapi.la: No such file or directory
libtool: link: `/opt/heimdal/lib/sparcv9/libgssapi.la' is not a valid libtool archive
gmake[3]: *** [libhdb.la] Error 1
gmake[3]: Leaving directory `/opt/ws/dists/Services/heimdal-1.2.1/lib/hdb'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/opt/ws/dists/Services/heimdal-1.2.1/lib/hdb'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/opt/ws/dists/Services/heimdal-1.2.1/lib'
gmake: *** [all-recursive] Error 1
How do I get libtool to ignore the old file & use the new one? Any help would be greatly appreciated.
Thanks.
-John

You probably have a shared library with a runpath that includes the location of the old libkrb5.so, and that does not include the location of the new version. The reference to libkrb5.so then can't be satisfied if you remove or rename the old directory. That dependency would also explain the linker complaint about the two copies of libkrb5.so when both are visible.
Run ldd on the various project libraries to find ones with a dependency on /opt/heimdal/lib/sparcv9/libkrb5.so. Rebuild them with a new runpath (-R option) that does not include /opt/heimdal/lib/sparcv9 but does include the directory containing the new library version.
If you can't remove /opt/heimdal/lib/sparcv9 from the runpath because the applciation needs other libraries in that directory, you need to replace the libkrb5.so in the directory with your new version. (I would rename the old directory so that you don't lose it.)
(Note: the -L option tells the linker where to look for libraries at program link time. The -R option tells the run-time loader where to look for libraries when the program is run.)
You also mention a ".la" file. I don't know what that is. I don't find a mention of such a thing in the Solaris Linker and Libraries Guide.

Possible name conflict flex - java

I have a string property 'comments' in data object A, it was working fine that the data was passing from flex to java, then because of some other properties in A, i need to add @XmlType and propOrder for A, then suddendly 'comments' is always null from flex to java, when other properties are passing ok, after many attempts, i change the property name from 'comments' to some other name and it works again (actual value is passed from flex to java).
So i am wondering, is it flex, web services, or jaxb that might have a name conflict with 'comments'? I have another property in A that also is null from flex to java, but this one is complex object that has a string property and a byte[] property, and it is null, does anyone have any thoughts/suggestions?
Thanks
Shannon

Thanks Michael, i will take a look. My other property is 'uploadedFile' of a class 'uploadedFile' which has 'data' and 'fileName' properties, so i ended up changing all these names, and now it works.
Shannon

Jndi name conflict found in

I have received a naming conflict when starting up App Server 7.
I am using the Sun Studio Enterprise.
The abstract schema name for the entity bean is Billercenter and everywhere else that the bean is referenced is billerCenter.
I am thinking that the server is complaining about the name not matching in the application module, but it won't let me change out the name. The following error is from the server.log. Anyone know what the fix is?
[12/May/2004:16:59:13] SEVERE ( 4516): EJB5090: Exception in creating EJB container [javax.naming.NameAlreadyBoundException [Root exception is org.omg.CosNaming.NamingContextPackage.AlreadyBound: IDL:omg.org/CosNaming/NamingContext/AlreadyBound:1.0]]
[12/May/2004:16:59:13] SEVERE ( 4516): appId=billerCenter_EJBModule moduleName=billerCenter_EJBModule ejbName=billerCenter
[12/May/2004:16:59:13] SEVERE ( 4516): LDR5012: Jndi name conflict found in [billerCenter_EJBModule]. Jndi name [ejb/Billercenter] for bean [billerCenter] is already in use.
[12/May/2004:16:59:13] SEVERE ( 4516): LDR5013: Naming exception while creating EJB container:
javax.naming.NameAlreadyBoundException. Root exception is org.omg.CosNaming.NamingContextPackage.AlreadyBound: IDL:omg.org/CosNaming/NamingContext/AlreadyBound:1.0
at org.omg.CosNaming.NamingContextPackage.AlreadyBoundHelper.read(AlreadyBoundHelper.java:60)
at org.omg.CosNaming._NamingContextExtStub.bind(_NamingContextExtStub.java:222)
at com.sun.jndi.cosnaming.CNCtx.callBindOrRebind(CNCtx.java:552)
at com.sun.jndi.cosnaming.CNCtx.bind(CNCtx.java:588)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:204)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:168)
at com.sun.ejb.containers.BaseContainer.initializeHome(BaseContainer.java:409)
at com.sun.ejb.containers.EntityContainer.initializeHome(EntityContainer.java:355)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:230)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.EJBModuleLoader.load(EJBModuleLoader.java:79)
at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:194)
at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:166)
at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:297)
at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:464)
at com.iplanet.ias.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:451)
at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:294)
at com.iplanet.ias.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:99)
at com.iplanet.ias.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
[12/May/2004:16:59:13] WARNING ( 4516): CORE5020: Error while loading ejb module
[12/May/2004:16:59:13] WARNING ( 4516): ADM5603:Event listener error [Error while loading EJB module [billerCenter_EJBModule]. Please refer to the server log for more details. ]

12/May/2004:16:59:13] SEVERE ( 4516): LDR5012: Jndi name conflict found in [billerCenter_EJBModule]. Jndi name [ejb/Billercenter] for bean [billerCenter] is already in use.
If you look at your deployment descriptor which should be ejb-jar.xml you s hould have more than 1 jndi entries which are identical for more than 1 ejbs ..

Help! NameAlreadyBound Exception, JNDI name conflict

Hi, I am using EJB 3.0 and I really have no idea on using JNDI. I read several queries and answers on this problem but I dont know how to solve it. When i go to ejb-jar.xml, I see very little information. Please help! Urgently needed. Any ideas will do, thanks!
EJB5090: Exception in creating EJB container [javax.naming.NameAlreadyBoundException: Use rebind to override]
appId=ESCM moduleName=ESCM-ejb_jar ejbName=SystemfunctionBean
LDR5012: Jndi name conflict found in [ESCM]. Jndi name [AHL.SystemfunctionRemote] for bean [SystemfunctionBean] is already in use.
LDR5013: Naming exception while creating EJB container:
javax.naming.NameAlreadyBoundException: Use rebind to override
at com.sun.enterprise.naming.TransientContext.doBindOrRebind(TransientContext.java:279)
at com.sun.enterprise.naming.TransientContext.bind(TransientContext.java:219)
at com.sun.enterprise.naming.SerialContextProviderImpl.bind(SerialContextProviderImpl.java:98)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.bind(LocalSerialContextProviderImpl.java:77)
at com.sun.enterprise.naming.SerialContext.bind(SerialContext.java:372)
at com.sun.enterprise.naming.SerialContext.bind(SerialContext.java:387)
at javax.naming.InitialContext.bind(InitialContext.java:363)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:215)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:168)
at com.sun.ejb.containers.BaseContainer.initializeHome(BaseContainer.java:948)
at com.sun.ejb.containers.StatelessSessionContainer.initializeHome(StatelessSessionContainer.java:220)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:671)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:184)
at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:113)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:322)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:216)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:189)
at com.sun.enterprise.server.ApplicationManager.applicationEnabled(ApplicationManager.java:754)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:914)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:892)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:445)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:160)
at com.sun.enterprise.admin.server.core.AdminNotificationHelper.sendNotification(AdminNotificationHelper.java:128)
at com.sun.enterprise.admin.server.core.ConfigInterceptor.postInvoke(ConfigInterceptor.java:109)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:97)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:56)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:142)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:109)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
CORE5021: Application NOT loaded: [ESCM]

12/May/2004:16:59:13] SEVERE ( 4516): LDR5012: Jndi name conflict found in [billerCenter_EJBModule]. Jndi name [ejb/Billercenter] for bean [billerCenter] is already in use.
If you look at your deployment descriptor which should be ejb-jar.xml you s hould have more than 1 jndi entries which are identical for more than 1 ejbs ..

Name conflict in the DTR in the consolidation workspace

Hello Experts,
While transporting the track, during assembly I am getting a name conflict in the DTR in the consolidation workspace. Any ideas on how to resolve this problem???
Thanks and Regards,
Divyata

Hi,
I got the solution.
Regards,
Divyata

NWDI: Name Conflict in Consolidation Track

Hi Experts,
We transported our development components from Dev(development) to Cons(consolidation) track.
It is throwing an error name conflict in CONS track.
I have tried to accept active version in cons track.But it was not allowing me to create an activity.
Error: FAILED: Checkout inactive DeltaV resource failed (Forbidden [(pre||post)-condition failed: DAV:access-denied])
Could anyone help on this issue?
Thanks in Advance.
Best Regards,
Arumugakarthika S

Dear Arumugakarthika,
the problem is most likely that the acl.xml in the following location is too restrictive:
http://<dtrhost>:<port>dtr/ws/system/config/active/ACLs/byPath/acl.xml
I assume it contains only access and read privileges for NWDI.Administrators.
To correct this please proceed as follows:
1. open up NWDS and log in to DTR with NWDI administrator user
2. check out the acl.xml file
3. since you will not be able to edit the acl.xml file from NWDS, locate it on your harddrive and edit it with other editor. Please also remove the read-only flag if needed.
4. check in the new version of the file through NWDS.
I add here a sample acl.xml which you can use as starting point for ACL permission settings.
<?xml version="1.0" encoding="UTF-8"?>
<acls>
<acl>
<resource>/</resource>
<ace>
    <all />
    <grant>
      <privilege>access</privilege>
      <privilege>read</privilege>
      <privilege>write</privilege>
      <privilege>checkin</privilege>
      <privilege>import</privilege>
      <privilege>export</privilege>
      <privilege>integrate</privilege>
      <privilege>adminA</privilege>
      <privilege>adminX</privilege>
    </grant>
    <description></description>
</ace>
<ace>
    <isgroup />
    <principal>NWDI.Developers</principal>
    <grant>
      <privilege>access</privilege>
      <privilege>read</privilege>
      <privilege>write</privilege>
      <privilege>checkin</privilege>
    </grant>
    <description></description>
</ace>
<ace>
    <isgroup />
    <principal>NWDI.Administrators</principal>
    <grant>
      <privilege>access</privilege>
      <privilege>read</privilege>
      <privilege>write</privilege>
      <privilege>checkin</privilege>
      <privilege>import</privilege>
      <privilege>export</privilege>
      <privilege>integrate</privilege>
      <privilege>adminA</privilege>
      <privilege>adminX</privilege>
    </grant>
    <description></description>
</ace>
</acl>
</acls>
I hope this helps.
Regards,
Ervin

[svn:bz-trunk] 20587: update the echoService destination name to qa.axis. EchoService to avoid a name conflict in ria package.

Revision: 20587
Revision: 20587
Author:   [email protected]
Date:     2011-03-03 14:11:37 -0800 (Thu, 03 Mar 2011)
Log Message:
update the echoService destination name to qa.axis.EchoService to avoid a name conflict in ria package.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/proxy-config.mods.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/dataTypesTest/p roxy-config.xml

[svn] 3512: rename flex4 mx.effects.easing to mx.effects. fxEasing to avoid a name conflict in the framework

Revision: 3512
Author: [email protected]
Date: 2008-10-07 13:28:56 -0700 (Tue, 07 Oct 2008)
Log Message:
rename flex4 mx.effects.easing to mx.effects.fxEasing to avoid a name conflict in the framework
Modified Paths:
flex/sdk/trunk/frameworks/gumbo-manifest.xml
flex/sdk/trunk/frameworks/mxml-2009-manifest.xml
flex/sdk/trunk/frameworks/projects/flex4/manifest.xml
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/Animation.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/FxAnimate.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/FxAnimateFilter.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/fxEasing/Constant.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/fxEasing/EaseInOut.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/fxEasing/IEaser.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/fxEasing/Linear.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/fxEasing/Power.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/fxEasing/Sine.as
Added Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/fxEasing/
Removed Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/easing/
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/CallAction.as

Thats good news.

How to resolve xjc method name conflict?

Hi! I'm having a problem with certain types of schema constructs and the method names in the xjc-generated classes. E.g., given the schema fragment:
<xs:element name="DocRef_type">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:integer">
<xs:attribute name="value" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="medline"/>
<xs:enumeration value="pubmed"/>
<xs:enumeration value="ncbigi"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
xjc (current release) fails on this schema, because it would generate overlapping method names: one getValue() to return the integer value, and one getValue() to return the string attribute named "value". Now, I know I can fix this by just changing 'name="value"' to 'name="somethingElse"' in the above attribute, but this breaks existing XML data we've already got that uses value="...".
Is there some way to tell xjc to use a different name mapping to resolve this conflict in the generated java class?
TIA for any tips,
- Paul

You can customize the name of the property representing the attribute. E.g.:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
jaxb:version="1.0">
<xs:attribute name="value" use="required">
<xs:annotation>
<xs:appinfo>
<jaxb:property name="attValue"/>
</xs:appinfo>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
-- Ed

Name conflict

There is a game in aur named enigma. I did a package for a game, that is named enigma, too. It was formerly known as oxyd, and then have been open sourced as enigma.
What to do? name the package enigma-oxyd?
# $Id: PKGBUILD,v 1.1 2005/10/09 19:03:37 judd Exp $
pkgname=enigma-oxyd
pkgver=0.92
pkgrel=1
pkgdesc="Enigma is a puzzle game inspired by Oxyd on the Atari ST and Rock'n'Roll on the Amiga. The object of the game is to find uncover pairs of identically colored Oxyd stones. Simple? Yes. Easy? Certainly not! Hidden traps, vast mazes, laser beams, and, most of all, countless hairy puzzles usually block your direct way to the Oxyd stones... "
depends=('sdl' 'sdl_ttf' 'sdl_mixer' 'sdl_image')
url="http://www.nongnu.org/enigma/"
groups=('game')
conflicts=('enigma')
source=(http://download.berlios.de/enigma-game/enigma-$pkgver.tar.gz)
#source=(http://savannah.nongnu.org/download/enigma/$pkgname-$pkgver.tar.gz)
md5sums=('4b1407c637ec5b4d452ba54392255c80')
build() {
cd $startdir/src/enigma-$pkgver
./configure --prefix=/usr/
make || return 1
make DESTDIR=$startdir/pkg install

Cerebral wrote:
Not so much in AUR as in extra.
07:53pm $ pacman -Ss enigma
extra/enigma 1.04-1
Enigma is a puzzle game involving falling blocks
OK
I would call it enigma-oxyd. The pkgdesc should be shortened though.

VI Name conflicts with "Open VI reference"

I am using LabView RT, where an application loads LLBs at runtime:
1- The user creates/compiles a LLB containg a VI that is loaded at runtime later
2- The user renames the contained VI to an enumerated name so that all names are always unique
3- The user uploads the LLB (containg the VIs with a unique name) to a LabView RT system
4- The LabView RT application openes all available VIs contained by the uploaded LLBs at runtime (the filename hints at the VI's unique name)
5- The LabView RT application executes the now opened VIs
My problem is step 2 where the user needs to rename the VI. This is because the RT application will not be able to distinguish between the opened VIs if their names are equal. I want to eliminate step 2 because it's error prone as the user always forgets to do the renaming or the user does the renaming in a wrong way (e. g. non-unique, typo).
A dirty hack would be to automatically replace all VI name strings (which are alidentical and like a placeholder) inside the LLB binary with unique ones at RT application's runtime. So the application takes over the renaming task.
Any other solution?

Hi Salim,
This CORBA support being moved from SP2 to next release.
Honghsi
Salim Djaffar wrote:
Andy Piper <[email protected]> wrote:
"Eric Green" <[email protected]> writes:
Andy Piper <[email protected]> wrote:
For what it's worth, except for the error message WTC appears to
be functioning fine in a clustered environment.Right. It will mostly work, but there are some issues with the CORBA
support.
When is the ballpark release date for SP2? Is WTC at SP1
now, or is this two updates away?I mean WLS 6.1 SP2. I do not know what the timeline is for these
things.
andy
--I also experienced the same problem, and I planned to go production within a month
or two.
Do you have any estimate when SP2 will be GA for public ?
salim

System Log Event ID 4321 every 30 seconds, system name conflict for a name not in use

-- Symptom --
System event log shows an error with event ID 4321 every 30 seconds:
The name "pac-1 :2d" could not be registered on the interface with IP address 172.20.51.206. The computer with the IP address 172.20.21.2 did not allow the name to be claimed by this computer.
-- Environment --
OS: Windows 7 x64 Enterprise
Network: Enterprise domain
DHCP: Yes
WINS: via DHCP
-- Additional information --
This computer was set up from an image. The image was built with the system being named 'pac-1'. This system's name was changed to 'pac-11' before (or possibly shortly after) joining the domain and now has a completely different name, and there
is no system on the network with the name 'pac-1' (there are 'pac-3', and other numbers, but no 'pac-1')
I have renamed the system with no change to the frequency of the error, and I cannot find 'pac-1' in the registry anywhere except for strings located in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons that list prior logons.
I've done my google research and have found great information for plenty of other people's situations, just not this one. Any helpful advice is welcome.
Thank you!

c0lorless wrote:
-- Symptom --
System event log shows an error with event ID 4321 every 30 seconds:
The name "pac-1 :2d" could not be registered on the
interface with IP address 172.20.51.206. The computer with the IP
address 172.20.21.2 did not allow the name to be claimed by this
computer.
-- Environment -- OS: Windows 7 x64 Enterprise
Network: Enterprise domain
DHCP: Yes
WINS: via DHCP
-- Additional information -- This computer was set up from an image. The image was built with the
system being named 'pac-1'. This system's name was changed to
'pac-11' before (or possibly shortly after) joining the domain and
now has a completely different name, and there is no system on the
network with the name 'pac-1' (there are 'pac-3', and other numbers,
but no 'pac-1')
I have renamed the system with no change to the frequency of the
error, and I cannot find 'pac-1' in the registry anywhere except for
strings located in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory
\Logons that list prior logons.
I've done my google research and have found great information for
plenty of other people's situations, just not this one. Any helpful
advice is welcome.
Thank you!
I'd check my WINS server's registration entries, if they contain an
entry with that NETBIOS name. If the machine with the ip-address
172.20.21.2 is not your WINS server you need to check, what services
etc. are running on that machine. Also look if the domain/workgroup
name, which is used by this machine is correct and identical to all
other machines.
Wolfgang

Excessive Name Conflicts

Similar Messages

Maybe you are looking for