equipment is not mapped 哈哈

HQL大小写敏感问题
本文探讨了在使用Hibernate查询语言(HQL)时遇到的大小写敏感问题,具体表现为查询所有记录时因类名大小写不一致导致的错误。通过对比两段几乎相同的代码,突出了Java类名在HQL查询中正确书写的重要性。
	public List allEquipment() {
		Session session = MySessionFactory.getSession();
		List list= new ArrayList();
		Transaction ts = null;
		try {
			ts = session.beginTransaction();
			String HQL = "select a from equipment as a order by a.id";
			Query query = session.createQuery(HQL);
			list = query.list();
			ts.commit();
		} catch (Exception e) {
			ts.rollback();
			System.out.println("查询所有,系统出现错误,原因为:");
			e.printStackTrace();
		}finally{
			MySessionFactory.closeSession();
		}
		return list;
	}

 上面这个和下面这个 有什么不同呢?不过上面这个就是不能运行 报这个错误:equipment is not mapped

	public List allEquipment() {
		Session session = MySessionFactory.getSession();
		List list = new ArrayList();
		Transaction ts = null;
		try {
			ts = session.beginTransaction();
			String HQL = "select a from Equipment as a order by a.id";
			Query query = session.createQuery(HQL);
			list = query.list();
			ts.commit();
		} catch (Exception e) {
			ts.rollback();
			System.out.println("查询所有,系统出现错误,原因为:");
			e.printStackTrace();
		}finally{
			MySessionFactory.closeSession();
		}
		return list;
	}

 注意sql 语句

上面:String HQL = "select a from equipment as a order by a.id";
下面:String HQL = "select a from Equipment as a order by a.id";
这个家伙大小写不行啊。。。

Extended VLANs (eVLAN) The eBridge architecture extends the 4K Virtual LAN (VLANs) defined by IEEE 802.1Q into a larger set of bridging domains called eVLANs. Ingress and egress bridging domain attributes are applied based on the packet eVLAN assignment. The eVLAN assignment mechanism is an extension of the legacy device Tag0 VID assignment mechanism. All legacy device Tag0 VID assignment mechanisms are replaced by the eVLAN assignment. The default eVLAN assignment is based on the packet VLAN Tag0 classification. If VLAN Tag0 is not found in the packet, the packet is assigned an eVLAN, based on the Default Port <eVLAN> configuration (PVID). For details regarding eVLAN assignment mechanisms, refer to Section 27, eVLAN/VLAN-ID Assignment and Tagging. 4.3 Extended VIDX (eVIDX) In legacy devices, a target VIDX is used to replicate a packet to a set of physical ports. In the eBridge architecture, the eVIDX is an extension of the VIDX paradigm to allow a packet to be replicated by the Layer2 Multicast Linked-List (L2MLL) engine to a set of virtual interfaces as well as physical ports. All forwarding engines can assign a target eVIDX value. If the eVIDX value is lower than a configurable threshold, the packet bypasses the L2MLL replication engine, and is replicated to a set of physical ports based on the VIDX port group. If the eVIDX assigned value is higher than a configurable threshold, the packet is replicated by the L2MLL engine to a set of target interfaces. The eVIDX is mapped to a L2MLL link-list via a lookup translation table. Each element of the linked-list contains a target egress interface assigned to the replication instance, as well as a set of various kinds of filters (for example, broadcast filter, unknown unicast filter, local switching filter, split horizon filter), and additional attributes. For details regarding the L2MLL engines, engine content and structure, full list of entries’ attributes, configuration, and usage, refer to Section 15.2, IP/L2-Multicast Linked List (MLL) Replicator Engines. Refer to Section 4.1.1.3, eVIDX L2MLL Replication Group to learn how to map a target ePort to an eVIDX group. eDSA Tag The eBridge architecture extends the DSA tag to include additional information such as the source and target ePort, eVLAN, and eVIDX fields. For interoperability with legacy devices, each physical port can be configured to support 4-byte, 8-byte, or the eDSA 16-byte DSA tag. The first 2 words of the eDSA tag are fully backward compatible (format and content) to the 4-byte and 8-byte DSA tags. Refer to Section 34, Centralized Switching Architecture for details of a special application of using 8-byte DSA tag to cascade legacy devices in a centralized switching architecture. For details on the eDSA tag format, refer to Section A, Extended DSA and eDSA Tag Formats. 翻译并解释
最新发布
09-29
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值