Invalid standard action 错误

Tomcat提示出现如下错误:
org.apache.jasper.JasperException: /carPage1.jsp(9,16) Invalid standard action

Invalid [in'vælid]意为 无效的,不能识别的

 我有一辆 <jsp:getProgerty name="myCar" property="make"/>   


<jsp:getProgerty>这里写错一个单词 导致的 property['prɔpəti]意思为性质、属性

看来动手和看书 学的东西差别太大了

useBean 写错也会有这样的问题...

刚开始学,写个文章纪念下......

配置tomcat 要加servlet-api.jar包,开始没弄,holloworld 没事,后面就有问题了...
class文件也要放对对方,书也到处是错误...悲剧
◆ cpssDxChPclRuleSet() GT_STATUS cpssDxChPclRuleSet ( IN GT_U8 devNum, IN GT_U32 tcamIndex, IN CPSS_DXCH_PCL_RULE_FORMAT_TYPE_ENT ruleFormat, IN GT_U32 ruleIndex, IN CPSS_DXCH_PCL_RULE_OPTION_ENT ruleOptionsBmp, IN CPSS_DXCH_PCL_RULE_FORMAT_UNT * maskPtr, IN CPSS_DXCH_PCL_RULE_FORMAT_UNT * patternPtr, IN CPSS_DXCH_PCL_ACTION_STC * actionPtr ) The function sets the Policy Rule Mask, Pattern and Action. Note APPLICABLE DEVICES: xCat3; AC5; Lion2; Bobcat2; Caelum; Aldrin; AC3X; Bobcat3; Aldrin2; Falcon; AC5P; AC5X; Harrier; Ironman; AAS. NOT APPLICABLE DEVICES: None. Parameters [in] devNum - device number [in] tcamIndex - index of the TCAM unit. (APPLICABLE DEVICES AC5) (APPLICABLE RANGES 0..1) [in] ruleFormat - format of the Rule. [in] ruleIndex - index of the rule in the TCAM. The rule index defines order of action resolution in the cases of multiple rules match with packet's search key. Action of the matched rule with lowest index is taken in this case With reference to Standard and Extended rules indexes, the partitioning is as follows: For DxCh and DxCh2 devices: Standard rules. Rule index may be in the range from 0 up to 1023. Extended rules. Rule index may be in the range from 0 up to 511. Extended rule consumes the space of two standard rules: Extended rule with index 0 <= n <= 511 is placed in the space of two standard rules with indexes n and n + 512. For DxCh3 device: The TCAM has up to 3.5K (3584) rows. See datasheet of particular device for TCAM size. Each row can be used as: 4 standard rules 2 extended rules 1 extended and 2 standard rules 2 standard and 1 extended rules The TCAM partitioning is as follows: Standard rules. Rule index may be in the range from 0 up to 14335. Extended rules. Rule index may be in the range from 0 up to 7167. Extended rule consumes the space of two standard rules: Extended rule with index 0 <= n < 3584 is placed in the space of two standard rules with indexes n and n + 3584. Extended rule with index 3584 <= n < 7168 is placed in the space of two standard rules with indexes n + 3584, n + 7168. For xCat3 and above devices: See datasheet of particular device for TCAM size. For example describe the TCAM that has 1/4K (256) rows. Each row can be used as: 4 standard rules 2 extended rules 1 extended and 2 standard rules 2 standard and 1 extended rules The TCAM partitioning is as follows: Standard rules. Rule index may be in the range from 0 up to 1K (1024). Extended rules. Rule index may be in the range from 0 up to 0.5K (512). Extended rule consumes the space of two standard rules: Extended rule with index 2n (even index) is placed in the space of two standard rules with indexes 4n and 4n + 1. Extended rule with index 2n+1 (odd index) is placed in the space of two standard rules with indexes 4n+2 and 4n + 3. [in] ruleOptionsBmp - Bitmap of rule's options. The CPSS_DXCH_PCL_RULE_OPTION_ENT defines meaning of each bit. Samples: [in] ruleOptionsBmp = 0 - no options are defined. Rule state is valid. [in] ruleOptionsBmp = CPSS_DXCH_PCL_RULE_OPTION_WRITE_INVALID_E - write all fields of rule to TCAM but rule's state is invalid (no match during lookups). [in] maskPtr - rule mask. The rule mask is AND styled one. Mask bit's 0 means don't care bit (corresponding bit in the pattern is not using in the TCAM lookup). Mask bit's 1 means that corresponding bit in the pattern is using in the TCAM lookup. The format of mask is defined by ruleFormat [in] patternPtr - rule pattern. The format of pattern is defined by ruleFormat [in] actionPtr - Policy rule action that applied on packet if packet's search key matched with masked pattern. For AAS and above devices actionPtr->egressPolicy is input field containing direction. Return values GT_OK - on success GT_BAD_PARAM - on wrong parameters GT_BAD_PTR - on null pointer GT_OUT_OF_RANGE - one of the parameters is out of range GT_HW_ERROR - on hardware error GT_TIMEOUT - after max number of retries checking if PP ready GT_NOT_APPLICABLE_DEVICE - on not applicable device Note The pattern and mask input structures should be set to zero by an application before assignment of fields. The function places all muxed fields to rule patern and mask by using bitwise OR operation. The function does not check validity of muxed (overlapped) fields. cpssDxChPclRuleSet()函数的主要功能是什么
09-23
在信息技术快速发展的背景下,构建高效的数据处理与信息管理平台已成为提升企业运营效能的重要途径。本文系统阐述基于Pentaho Data Integration(简称Kettle)中Carte组件实现的任务管理架构,重点分析在系统构建过程中采用的信息化管理方法及其技术实现路径。 作为专业的ETL(数据抽取、转换与加载)工具,Kettle支持从多样化数据源获取信息,并完成数据清洗、格式转换及目标系统导入等操作。其内置的Carte模块以轻量级HTTP服务器形态运行,通过RESTful接口提供作业与转换任务的远程管控能力,特别适用于需要分布式任务调度与状态监控的大规模数据处理环境。 在人工智能应用场景中,项目实践常需处理海量数据以支撑模型训练与决策分析。本系统通过整合Carte服务功能,构建具备智能调度特性的任务管理机制,有效保障数据传递的准确性与时效性,并通过科学的并发控制策略优化系统资源利用,从而全面提升数据处理效能。 在系统架构设计层面,核心目标在于实现数据处理流程的高度自动化,最大限度减少人工干预,同时确保系统架构的弹性扩展与稳定运行。后端服务采用Java语言开发,充分利用其跨平台特性与丰富的类库资源构建稳健的服务逻辑;前端界面则运用HTML5、CSS3及JavaScript等现代Web技术,打造直观的任务监控与调度操作界面,显著提升管理效率。 关键技术要素包括: 1. Pentaho数据集成工具:提供可视化作业设计界面,支持多源数据接入与复杂数据处理流程 2. Carte服务架构:基于HTTP协议的轻量级服务组件,通过标准化接口实现远程任务管理 3. 系统设计原则:遵循模块化与分层架构理念,确保数据安全、运行效能与系统可维护性 4. Java技术体系:构建高可靠性后端服务的核心开发平台 5. 并发管理机制:通过优先级调度与资源分配算法实现任务执行秩序控制 6. 信息化管理策略:注重数据实时同步与系统协同运作,强化决策支持能力 7. 前端技术组合:运用现代Web标准创建交互式管理界面 8. 分布式部署方案:依托Carte服务实现多节点任务分发与状态监控 该管理系统的实施不仅需要熟练掌握Kettle工具链与Carte服务特性,更需统筹Java后端架构与Web前端技术,最终形成符合大数据时代企业需求的智能化信息管理解决方案。 资源来源于网络分享,仅用于学习交流使用,请勿用于商业,如有侵权请联系我删除!
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值